Compact Message Storage

It's still a work in progress.

[x] Remove messages from EditorLinter (API Breaking </3 But no package I know uses this so it's okay)
[x] Store all messages in Linter
[x] Deprecate but still support {get, set, delete, observe}ProjectMessages in favor of {get, set, delete, observe}Messages
[ ] Do some other stuff

This PR would lay foundations for a beautiful internal API

What do you think of this idea?
/cc @AsaAyers @lierdakil @k2b6s9j

Nice, it makes more sense imho to have Messages instead of ProjectMessages.
What method would be made public?

They are both public, but ProjectMessages will be removed soon.

I'm a little bit concerned that Linter is becoming a "super-class". I'm generally against super-classes.
So let me propose something a little bit different: have a singleton MessageStorage module (see here for a brief overview), or at least single instance of it, and handle message storage, classification, etc there.
If you choose to go singleton module route, you don't need to thread it around even, just require it where it's used (since Node caches requires, it works as a single instance).
Does that sound reasonable?

@lierdakil I agree with you, but I don't think that's the scope of the PR. We can do it after, I like the idea of having a store for these.

@iam4x, if @steelbrain is doing it now, he might as well do it right the first time around. There is a whole lot of other possible code enhancements, so it's not like we'll run out of PR material any time soon. Enforcing encapsulation and module separation at the early stage is important, because after a while, refactoring horribly entangled parts out becomes a huge undertaking, and can lead to unavoidable API breakage, which is bad, for obvious reasons. That said, it's not my repo (and I prefer it this way), so you do have a final say in the matter.

Guys, a lot of areas of our codebase (esp. LinterViews) are un-beautiful, they could be made better looking by rewriting them in ES6,thoughts?

Only one todo to kill. :muscle:

Please stick with CS, especially if you still think about getting this into core.

@lierdakil I reverted all the classes I wrote in JS back to coffee. I am starting to love it :sweat_smile:

CoffeeScript is fine, provided you don't care about ever getting the ability to detect unused or undefined variables. Then you're screwed

So I removed the editorMessages from the storage to keep the messages from file scoped linters not available in the project tab, but then I ran into other problems like, if the editor that set it's messages as value for that linter, if it's destroyed what are we gonna do then? or if it's switched from active to non-active, that sort of complications started to arise, and what if the editor-linter is destroyed, are we gonna remove all of the file-scoped linter's messages from the message registry.
So I have decided to keep a private @messages var in editor-linter, but the API of MessageRegistry remains the same.

I think I am gonna play wit this more, using the eye of performance.

Okay guys so I did some profiling with 266 messages and here's the results

so the thing that's taking most of our time is the regex parser we use, we might wanna switch to pure js regex (/cc @AsaAyers (it's coffeelint)). other than that, It's just appendChild and render Custom Element components (Message::attachedCallback) which is a DOM thing that we can't optimize.
Please note that the machine I did this profiling on is running an ordinary HDD and 4th gen 1.9 i5 intel processor. so I think this PR is quite efficient.

I need some testers people, our automated test coverage isn't very good. and I am gonna target it in my next PR where we make the modules work in isolated env.

(wrong button click)

@steelbrain linter-coffeelint doesn't use a XRegExp, so your conclusion there is wrong. That parse is actually inside coffeelint. I think that's JSON.parse becuase I don't see a parse() in CoffeeLint.

If you really want to profile the right thing, you should use a CLI linter so the internals of how the linter runs doesn't show up in your profile

Merging in to keep the pace of progress (been almost a week since this is open), there have been zero known non-fixed bugs in this PR.
Gonna work on making the modules work isolated in the next PR (It'll help us write tests for them).


[BUG]

Describe the bug
When I try to set ETA : 0.8 I have an error
To Reproduce
 Traceback (most recent call last):   File "prd.py", line 2125, in <module>     do_run(batch_image)   File "prd.py", line 1127, in do_run     samples = do_sample_fn(init, args.steps - cur_t - 1)   File "prd.py", line 1100, in do_sample_fn     eta=eta,
Desktop (please complete the following information):

OS: WINDOWS 11
GPU and VRAM: NVIDIA RTX3060Ti 8GB
CUDA Version 11.7

Additional context
Thank you

I believe this is the same issue as you asked about with clamp max. Both are schedules. I haven't used PRD in over a month, unless something's changed there isn't many bugs I was aware of and the ones there are shouldn't occur within normal operation of PRD.

If you post your gui_settings file maybe I can be more helpful.

Also are you 100* certain that's the whole error?

Also are you 100* certain that's the whole error?

Traceback (most recent call last):   File "prd.py", line 2125, in <module>     do_run(batch_image)   File "prd.py", line 1127, in do_run     samples = do_sample_fn(init, args.steps - cur_t - 1)   File "prd.py", line 1100, in do_sample_fn     eta=eta, NameError: name 'eta' is not defined
I have no more errors

Sorry, I forgot 'eta' is not defined

I have eta is not defined error too if I change the eta and clamp max.

Sorry, I forgot 'eta' is not defined

I think you can't change eta

I have eta is not defined error too if I change the eta and clamp max.

Are you using PRS, or PRD? I will assume PRD in which case, if you want to change clamp_max and eta from auto, you must format the value as a schedule as seen in the fields to the right in this picture.

I use PRD: Hey thanks for the quick reply, so I copied the format of cut ic pow over to clamp max and I got an error before saying “could not convert string to float”. Can you tell me what format works for you in there? And when I enter in the prompt replacing the default prompt, it’s completely different than it should actually be. (I know this from disco diffusion on colab)


Publish standup submissions in single thread

Publish user submissions as threaded messages. Add a customizable config to publish as top post or threaded.

Added feature in 5880e5792886cd9bf72b56263400bdca2f38e088


Fixes "the SQL engine automatically determines when to user them"

:slightly_smiling_face:

@bchavez : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good. Thanks!


New maintainers can't approve PRs

Noted by @Susurrus.
I'm considering attempting to move us to bors-ng which has some additional features on top of bors / homu:

it's actively maintained
it can batch PRs to merge multiple with one CI run

@Susurrus

@kamalmarhubi There's a synchronize button on the homu website and it asked for permissions to my account and nix-rust on GitHub. Do I need to do that so that I recognizes me or something?

Maybe! Give it a shot, unless the permissions are not to your liking.

👍 on moving to Bors!

@nix-rust/nix-maintainers FYI @homu is no more. The new way to approve PRs is bors r+, or bors r=username.


[FLINK-36009] Architecture tests refactor

Created the module flink-connector-jdbc-architecture to have all tests, we need to add the modules as dependency to validate that module..

Hi, @eskabetxe Thank you for your hard work. LGTM on the whole just the commit message header.
Would you mind helping update it ? thx~

fixed, the incorrect one was the PR that was using the Epic

@1996fanrui can you check

@leonardBang @MartijnVisser can you help here..


working with low frame rates

Hi,
I'm trying your project mv-extractor to get timestamp from the camera.
While in 30 FPS it works very nice, on 2 FPS I have a delay of about 3-4 seconds between the time that  the camera prints on the frame to the timestamp that returns from the mv-extractor.
is it possible to get high accuracy in low rates or it is only working on high rates?
I added an image from a camera I have: the white text on the image is the time that the camera prints on the frame. the blue text is the timestamp that arrived from the camera. you can see a time diff of 4 seconds
thanks.

Hey b1q2,
is that an IP camera running on the RTSP protocol? And if so, does it support the ONVIF standard? This is necessary because mv-extractor requires the camera to send RTCP sender reports to calculate the mapping between stream time and wall time.
But I honestly tried this feature only on the camera that I was using in the project back then. So, I don't want to give any guarantees that this works for all cameras.
I may also remove this feature in the future as it is not really related to the motion vector extraction. I only included it, because I used the mv-extractor as part of a larger project and had to move the timestamp estimation somewhere.

Hi Lockas,
Thanks for yor reply.
I'm using 'Dahua' as my IP camera. it seems that it is running on RTSP and supports RTCP reports.
in the code I'm running debug mode and I get theese two values both true:

packet.synced = 1
this->is_synced = 1

Can you tell us what camera you used getting these good results, and what was the frame-rate?
Do you know if the timestamp that returning from the camera is the time of the 'capturing' or the time of the 'sending' of the packet?
thanks.

I used the Dahua DH-SD22204T-GN and DH-SD22204T-GN. Regarding the frame rate, I am not sure anymore. Most likely it was configured to run at 1080p resolution with 30 Hz frame rate.
The camera sends both RTSP packets and RTCP sender reports. The RTSP packets contain only the stream time while the RTCP sender reports contain a mapping from the stream time to UTC time. From this, the UTC time at which the RTSP packet was assembled by the camera can be derived. And that is what mv-extractor provides you with in the "timestamp" value. I am honestly not sure, why this approach should break down when the frame rate is slowed.
Whether the timestamp in the RTSP packet represents the time of capture or sending, I am not sure. That should be specified in the RTSP protocol and if not it is probably left to the camera manufacturer to decide. However, the latency within the camera is probably in the order of milliseconds, whereas I encountered network latencies in the order of 30 seconds.

Closing due to inactivity. Feel free to reopen for further discussion.


Doc generation adds bogus version

https://github.com/spring-cloud/spring-cloud-static/commit/a8de150b3479e26c0cc47f4d31b69f0ddacdd9aa
https://github.com/spring-cloud/spring-cloud-static/commit/6df82c6b8e52952edfd32e8dda963b58228cd5c0
https://github.com/spring-cloud/spring-cloud-static/commit/bd6bf60f9ec7dad9a1dbdbc1b7b421306fa9a1d3
https://github.com/spring-cloud/spring-cloud-static/commit/a7173d3e1a9a57741667b8b11499ca061945811a

seems like the version here is what influences the version displayed in the docs https://github.com/spring-cloud-samples/scripts/blob/master/docs/pom.xml#L16

Yup it used to be 1.3.5.BUILD-SNAPSHOT prior to
https://github.com/spring-cloud-samples/scripts/commit/1403f3b01b75a405b7e10ad289ee47bdac36aba7#diff-48fabae9c2e321b2ab4d99057d5dc32eR8

We could change it to Greenwich.BUILD-SNAPSHOT and have it match the release version (with some work via the meta-releaser I guess)

My guess is the thing that is inserting the version is using the wrong property. There are properties in that pom for the release train.

maybe, I am sure @marcingrzejszczak knows for sure ;)

The meta-releaser also appears to not be trying to generate the documentation, at least I couldnt see it in the Greenwich.RC2 release https://jenkins.spring.io/view/Spring Cloud/view/Releaser/job/spring-cloud-meta-releaser/107/consoleFull


Issue with k8s.io/docs/tasks/administer-cluster/dns-debugging-resolution/

Fixes #15304

Verified.
/lgtm
/approve

https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/phases/addons/dns/manifests.go#L224


How to use writeCharacteristicWithResponseForDevice()?

I didn't way is right that write hex string to my board, anybody know that? i did a test my board by free BLE scanner, it's work.
Please refer screenshot that write '1b01' hex string. how can i do same thing on my app?

it's a BLE scanner NOT my app, just for test

Values are accepted in Base64 format, so you need to convert your hexadecimal string representation to Base64 in:

binary form: 1B02 is equal to GwI=.
string form: 1B02 -> 31423032 -> MUIwMg== / MUIwMgA= (null terminated)

@Cierpliwy it's work, thank you so much!


MIDIComponent compatibility with framer.cloud / iFrames

@eelco @nvh
Needs testing.
In reference to
https://www.facebook.com/groups/760188533992744/permalink/1518013801543543/

Cherry picked the commit that uses the parent.


Fix stats

Make declaration default to an empty dict
When we query declarations for stats we need to be able to look inside them. PostgreSQL complains if you try to query into a null value.
Make stats handle null declarations
There was a bug fixed in the previous commit that would result in JSON 'null' values for the supplier declaration which would in turn cause the stats queries to fail. As this is a subtle bug and the stats are depended on they need to be pretty robust. This change excludes JSON 'null' values from the query.

"Too many blank lines"

Other than that the code looks good and tests pass locally - :+1: once PEP8 is appeased.


history endpoint

It would help for the proxy (and the registry too, I guess) to have an endpoint that tells you what version it is.

Rather than inject a version number, there will be a history file that the registry and proxy serve up at the /history endpoint.  The history is just a plaintext file.


Can't reproduce results with pretrained weights

Hi,
thanks a lot for your great work and efforts to release code and pretrained models!
I followed your instructions for environment setup and used your data .pkl and pretrained weights.
Using the provided inference and visualization commands does not reproduce your results for  me.
Sadly, all detection and segmentation metrics are close to zero:
mAP: 0.0000
mATE: 1.0000
mASE: 1.0000
mAOE: 1.0000
mAVE: 1.0000
mAAE: 1.0000
NDS: 0.0000
Eval time: 20.6s

Per-class results:
Object Class    AP      ATE     ASE     AOE     AVE     AAE
car     0.000   1.000   1.000   1.000   1.000   1.000
truck   0.000   1.000   1.000   1.000   1.000   1.000
bus     0.000   1.000   1.000   1.000   1.000   1.000
trailer 0.000   1.000   1.000   1.000   1.000   1.000
construction_vehicle    0.000   1.000   1.000   1.000   1.000   1.000
pedestrian      0.000   1.000   1.000   1.000   1.000   1.000
motorcycle      0.000   1.000   1.000   1.000   1.000   1.000
bicycle 0.000   1.000   1.000   1.000   1.000   1.000
traffic_cone    0.000   1.000   1.000   nan     nan     nan
barrier 0.000   1.000   1.000   1.000   nan     nan

-*-*-*-*-*-*-*-*-*-*threshhold:1.5-*-*-*-*-*-*-*-*-*-*
cls:divider done in 10.671474s!!
cls:ped_crossing done in 1.378579s!!
cls:boundary done in 11.997211s!!

+--------------+-------+--------+--------+-------+
| class        | gts   | dets   | recall | ap    |
+--------------+-------+--------+--------+-------+
| divider      | 27332 | 88237  | 0.085  | 0.003 |
| ped_crossing | 6406  | 24793  | 0.049  | 0.001 |
| boundary     | 21050 | 187920 | 0.114  | 0.002 |
+--------------+-------+--------+--------+-------+
| mAP          |       |        |        | 0.002 |
+--------------+-------+--------+--------+-------+
divider: 0.001115116495687592
ped_crossing: 0.00023997755279954922
boundary: 0.0007757550420137704
map: 0.0007102830301669705

Also the resulting visualizations look distorted (similar to #8 :

I used the VAD_base_stage_2.py config with the provided pretrained weights.

Can you help me figuring out what I configured wrong? Do the pretrained weights match the given config and data preparation?
Can you provide the result metrics of stage-1 and stage-2 training as well

Thank you so much in advance for your help!

I might have found a solution:

The img_norm_cfg was changed in 156a74465a2ecd0d988cb4ecca46cca371492e4c as discussed in #9. It seems as if this config does not fit the pretrained weights. Changing the corresponding line to:
img_norm_cfg = dict(
   mean=[103.530, 116.280, 123.675], std=[1.0, 1.0, 1.0], to_rgb=False)

seems to fix the issue (see visualization results above) but I need to continue the investigation.

Hi,
When I executed the visulation script using the checkpoint provided by the author, an error occured,
Python command: python tools/analysis_tools/visualization.py --result-path test/VAD_base_stage_2/Sat_Sep__9_02_04_54_2023/pts_bbox/results_nusc.pkl --save-path vis_results
Error:
Exception has occurred: ValueError (note: full exception trace is shown but execution is paused at: _run_module_as_main)
all the input arrays must have same number of dimensions, but the array at index 0 has 2 dimension(s) and the array at index 1 has 3 dimension(s)
File "/workspace/projects/VAD/projects/mmdet3d_plugin/core/bbox/structures/nuscenes_box.py", line 268, in render_fut_trajs_grad_color
fut_coord = np.concatenate((self.center[np.newaxis, :2], fut_coord), axis=0)
File "/workspace/projects/VAD/tools/analysis_tools/visualization.py", line 567, in visualize_sample
box.render_fut_trajs_grad_color(axes, linewidth=1, mode_idx=mode_idx, fut_ts=6, cmap='autumn')
File "/workspace/projects/VAD/tools/analysis_tools/visualization.py", line 315, in lidiar_render
visualize_sample(nusc, sample_token, gt_annotations, pred_annotations,
File "/workspace/projects/VAD/tools/analysis_tools/visualization.py", line 719, in render_sample_data
lidiar_render(sample_toekn, pred_data, out_path=out_path,
File "/workspace/projects/VAD/tools/analysis_tools/visualization.py", line 747, in
render_sample_data(sample_token_list[id],
File "/opt/conda/envs/vad/lib/python3.8/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/opt/conda/envs/vad/lib/python3.8/runpy.py", line 192, in _run_module_as_main (Current frame)
return _run_code(code, main_globals, None,
ValueError: all the input arrays must have same number of dimensions, but the array at index 0 has 2 dimension(s) and the array at index 1 has 3 dimension(s)
Have you ever met this problem? If so could you give me some suggestions to solve this problem? Thank you very much!

I might have found a solution:  The img_norm_cfg was changed in 156a744 as discussed in #9. It seems as if this config does not fit the pretrained weights. Changing the corresponding line to:
img_norm_cfg = dict(
   mean=[103.530, 116.280, 123.675], std=[1.0, 1.0, 1.0], to_rgb=False)

seems to fix the issue (see visualization results above) but I need to continue the investigation.

Yes, we have updated the ‘img_norm_cfg’ based on the suggestion from this issue, which is different when we train the model. This is the reason for the problem you encountered here. In the latest commit, we have included an explanation of this problem to help people reproduce results correctly. Thank you for your valuable suggestion.


CI: update label for test-bsd job

rationale: I think it would be easier for a new developer looking into the CI to understand that this is a different job from the larger test job.
This is a TODO item I found while working on PR #195.

This naming convention is also used in other tests such as test (aarch64-unknown-linux-gnu) run on Cirrus Ci, so I think it is fine as it is.


Hard to find conceptual documentation on device groups

The link for "device groups" inside the sentence "The steps in this topic assume that you are familiar with the concepts of Azure Sphere tenants, products, and device groups." takes me to a how-to page about how to manage device groups.  I expected it to take me to conceptual material about what a device group actually is.  The CLI docs at https://docs.microsoft.com/en-us/azure-sphere/reference/azsphere-device-group?tabs=cliv2beta are better, at telling me what configuration options are available for a device group.

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

ID: 3852d5e3-85a2-2f35-35c0-1f68315e44d4
Version Independent ID: aeff4fde-94ea-e00e-b257-a8bfe755946f
Content: Manage Azure Sphere device groups
Content Source: AzureSphere/articles/deployment/manage-device-groups.md
Product: azure-sphere
GitHub Login: @prabhushyja
Microsoft Alias: azurespheredocs

@BarryBo Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Doc has been updated with correct links.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


os: panic: runtime error: slice bounds out of range

What version of Go are you using (go version)?
go version go1.9 linux/amd64
Does this issue reproduce with the latest release?
Yes (both stable as well as master).
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/work"
GORACE=""
GOROOT="/opt/google/go"
GOTOOLDIR="/opt/google/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build311345589=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"

What did you do?
A FUSE test from our test suite started panicking when upgrading to Go 1.9. I'm not really sure whether we're doing some bad API call, but the panic seems to originate from within the os file handling.
$ go get -v github.com/ethereum/go-ethereum/swarm/fuse
$ go test -v github.com/ethereum/go-ethereum/swarm/fuse
=== RUN   TestFUSE
=== RUN   TestFUSE/mountListAndUmount
=== RUN   TestFUSE/maxMounts
=== RUN   TestFUSE/remount
=== RUN   TestFUSE/unmount
=== RUN   TestFUSE/unmountWhenResourceBusy
=== RUN   TestFUSE/seekInMultiChunkFile
=== RUN   TestFUSE/createNewFile
=== RUN   TestFUSE/createNewFileInsideDirectory
=== RUN   TestFUSE/createNewFileInsideNewDirectory
=== RUN   TestFUSE/removeExistingFile
=== RUN   TestFUSE/removeExistingFileInsideDir
=== RUN   TestFUSE/removeNewlyAddedFile
=== RUN   TestFUSE/addNewFileAndModifyContents
panic: runtime error: slice bounds out of range [recovered]
	panic: runtime error: slice bounds out of range

goroutine 1500 [running]:
testing.tRunner.func1(0xc420e08000)
	/opt/google/go/src/testing/testing.go:713 +0x29d
panic(0x8fdfa0, 0xed51d0)
	/opt/google/go/src/runtime/panic.go:502 +0x266
internal/poll.(*FD).Write(0xc420d94b40, 0xc4206ee8f0, 0x6, 0x8, 0x0, 0x0, 0x0)
	/opt/google/go/src/internal/poll/fd_unix.go:227 +0x373
os.(*File).write(0xc420cdf0f8, 0xc4206ee8f0, 0x6, 0x8, 0xc420cdf0f8, 0x6, 0x0)
	/opt/google/go/src/os/file_unix.go:235 +0x4e
os.(*File).Write(0xc420cdf0f8, 0xc4206ee8f0, 0x6, 0x8, 0x0, 0x0, 0x0)
	/opt/google/go/src/os/file.go:140 +0x72
github.com/ethereum/go-ethereum/swarm/fuse.(*testAPI).addNewFileAndModifyContents(0xc42028e020, 0xc420e08000)
	/tmp/go/src/github.com/ethereum/go-ethereum/swarm/fuse/swarmfs_test.go:660 +0xc42
github.com/ethereum/go-ethereum/swarm/fuse.(*testAPI).(github.com/ethereum/go-ethereum/swarm/fuse.addNewFileAndModifyContents)-fm(0xc420e08000)
	/tmp/go/src/github.com/ethereum/go-ethereum/swarm/fuse/swarmfs_test.go:833 +0x34
testing.tRunner(0xc420e08000, 0xc42005be50)
	/opt/google/go/src/testing/testing.go:748 +0xc0
created by testing.(*T).Run
	/opt/google/go/src/testing/testing.go:791 +0x2b1

What did you expect to see?

What did you see instead?
Boom.

Tracking issue on the Ethereum repo: https://github.com/ethereum/go-ethereum/issues/15216

I assume this is repeatable.  I don't see any problem in the code, unless syscall.Write for some reason incorrectly returns a very large positive value.
Can you do some debugging to find out what the slice indexes are when the panic occurs?  Thanks.

go version go1.9 linux/amd64
/opt/google/go/src/internal/poll/fd_unix.go:227

It that really go1.9, not a git revision? Line 227 is return n, err:
   224	func (f *File) pread(b []byte, off int64) (n int, err error) {
   225		n, err = f.pfd.Pread(b, off)
   226		runtime.KeepAlive(f)
   227		return n, err
   228	}

/opt/google/go/src/os/file_unix.go:235

/opt/google/go/src/internal/poll/fd_unix.go:227

Is that really go1.9, not a git revision? Line 235 is return n, err:
   232	func (f *File) write(b []byte) (n int, err error) {
   233		n, err = f.pfd.Write(b)
   234		runtime.KeepAlive(f)
   235		return n, err
   236	}

and line 227 is continue:
   225			if err == syscall.EAGAIN && fd.pd.pollable() {
   226				if err = fd.pd.waitWrite(fd.isFile); err == nil {
   227					continue
   228				}
   229			}

@ianlancetaylor Will do!
@opennota I may have pasted the trace from master here, didn't notice there's a diff, but 1.9 panics the same way.

@ianlancetaylor I've added a print statement inside internal/poll/fd_unix.go, and syscall.Write indeed returns twice the size of my input array (I'm writing a slice of length 6, and syscall.Write returns 12, which blows at the next iteration).

So, you've found your problem; it must be in your FUSE driver.  I think it's reasonable for Go to assume that syscall.Write returns -1 on error and the number of bytes written on success, and I think it's reasonable for Go to assume that if it passes 6 bytes to Write that no more than 6 bytes will be written.  I don't think it should be necessary for the Go standard library to take precautions against other return values.  I'm going to close this issue.

Well, "my" fuse driver works perfectly well with Go 1.7.x and Go 1.8.x, so
it might very well be that the driver is buggy, but Go 1.9.0 breaks
something that previous versions could handle. So I wouldn't be so quick to
close.
On Oct 4, 2017 00:40, "Ian Lance Taylor"<EMAIL_ADDRESS>wrote:

Closed #22102 https://github.com/golang/go/issues/22102.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/22102#event-1276888820, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAH6GfxPtm6ecVOAjfKuEuJ7SLeZLUs8ks5soqnWgaJpZM4PqeGw
.

Also as far as I know Go is supposed to be a safe language, not one that
goes belly up on an underlying software or hardware error. Seems to be a
very hand wavey approach to allow the stdlib to crash on IO.
On Oct 4, 2017 09:34, "Péter Szilágyi"<EMAIL_ADDRESS>wrote:

Well, "my" fuse driver works perfectly well with Go 1.7.x and Go 1.8.x, so
it might very well be that the driver is buggy, but Go 1.9.0 breaks
something that previous versions could handle. So I wouldn't be so quick to
close.
On Oct 4, 2017 00:40, "Ian Lance Taylor"<EMAIL_ADDRESS>wrote:

Closed #22102 https://github.com/golang/go/issues/22102.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/22102#event-1276888820, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAH6GfxPtm6ecVOAjfKuEuJ7SLeZLUs8ks5soqnWgaJpZM4PqeGw
.

@karalabe Yes, the Go code has changed, and that may well affect the behavior when using a broken FUSE driver (assuming the FUSE driver is indeed broken).  But we can't promise to retain precisely the same behavior in all cases for each new Go release.  If we did, we may as well not make Go releases.
Go is intended to be a safe language.  That does not mean that it should never crash.  Quite the opposite.  It means that it should not behave unexpectedly.  For example, it should not continue running after an erroneous pointer reference.  If my earlier analysis is correct then the behavior here is consistent with that goal.  Looking at Go 1.8, it appears that if syscall.Write returns an incorrect value that the os package would return that incorrect value back to the caller of os.(*File).Write (I didn't test this, this is just from reading the code).  In other words, if syscall.Write fails to implement its API, then os.(*File).Write would fail to implement its API.  In those terms, although the error handling is terrible, this is actually a step forward.
To be honest, if I were in your position, I would be pleased: a new Go release may have found a bug in the FUSE driver.  That is a good thing.  So I'm a little bit befuddled by your suggestion that this change in behavior is a bug in Go.

Hello,
I just encountered the same issue after recompiled an existing internal software that use Minio with GoLang 1.10.
No issue with GoLang 1.9.4.
panic: runtime error: slice bounds out of range

goroutine 933 [running]:
bytes.(*Buffer).grow(0xc420170bd0, 0x200, 0xc4200aa050)
	/usr/lib/go/src/bytes/buffer.go:139 +0x297
bytes.(*Buffer).ReadFrom(0xc420170bd0, 0xda10c0, 0xc420663460, 0x7f8b73181120, 0xc420170bd0, 0x1)
	/usr/lib/go/src/bytes/buffer.go:204 +0x48
io.copyBuffer(0xda0020, 0xc420170bd0, 0xda10c0, 0xc420663460, 0x0, 0x0, 0x0, 0xbe0aa0, 0x13, 0x18)
	/usr/lib/go/src/io/io.go:386 +0x31a
io.Copy(0xda0020, 0xc420170bd0, 0xda10c0, 0xc420663460, 0x10, 0x0, 0x0)
	/usr/lib/go/src/io/io.go:362 +0x5a
io.CopyN(0xda0020, 0xc420170bd0, 0xda1720, 0xc4202e6000, 0x10, 0x10, 0x0, 0x0)
	/usr/lib/go/src/io/io.go:338 +0x8b
xxx/xxx/vendor/github.com/minio/minio-go/pkg/encrypt.(*CBCSecureMaterials).Read(0xc420376480, 0xc445120000, 0x24000000, 0x24000000, 0xca40, 0x0, 0x0)

@protheusfr This issue is closed.  It is very unlikely that you are seeing the same problem: the stack trace you show is completely different.  Please open a new issue, or ask on a forum; see https://golang.org/wiki/Questions.  Thanks.

Ok no pb.


Display source Dockerfile of the image based on e.g. LABEL metadata

Hi,
Would it be possible to add a feature where you can somehow specify source Dockerfile for given image stored in docker registry and harbor would display it?
e.g. I can think of using LABEL metadata from image to populate some UI component

Hi pmihalcin
In my personal opinion,  I can't image what kind of scenarios the Dockerfile can be used.
And Harbor is a authenticate registry(v2),  it must compatible official registry protocol.
expect other's opinion :)


cronjob for wis2box data archive never runs

I noted that the daily archive job on the future demo-wis2box has never runs (it's been up for 7 days) . If I run it manually from inside the wis2box-container it runs correctly.

cron was not installed, fixed in minio-updates

I still don't see files being archived on demo.wis2box.wis.wmo.int re-opening this until I can demonstrate that it is fixed

Implemented in #275


Trial PR for using scalafmt

enables sbt plugin for scalafmt in sbt
adds travis test requiring scalafmt for PR
formats everything in src/
formats build.sbt

Contributor Checklist

[x] Did you add Scaladoc to every public function/method?
[NA] Did you update the FIRRTL spec to include every new feature/behavior?
[x] Did you add at least one test demonstrating the PR?
[NA] Did you delete any extraneous printlns/debugging code?
[x] Did you specify the type of improvement?
[x] Did you state the API impact?
[x] Did you specify the code generation impact?
[x] Did you request a desired merge strategy?
[x] Did you add text to be included in the Release Notes for this change?

Type of Improvement
Code refactor. Style only. Force code to follows standard scalafmt
API Impact
No impact on API
Backend Code Generation Impact
No consequences for code generation
Desired Merge Strategy
Squash on merge
Release Notes
From this PR on all firrtl PR must follow scalafmt rules. This will be enforced in CI.
Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (1.2.x, 1.3.0, 1.4.0) ?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you mark as Please Merge?

LGTM, but requesting review from @freechipsproject/firrtl-reviewers since I don't really know what the agreed upon .scalafmt.conf is supposed to look like. can you push a commit with a bad formatting change to one of the .scala files just to sanity check CI.

Superseded by PR #1848


TextField + multiline -> React does not recognize the multiLine prop on a DOM element

Code example:
  <FormControl>
    <InputLabel htmlFor={props.helper}>{props.title}:</InputLabel>
    <TextField
      hintText="Your text here..."
      multiline={true}
      rows={3}
      rowsMax={5}
    />
  </FormControl>

Result (tested on Chrome):
"React does not recognize the multiLine prop on a DOM element"
"@material-ui/core": "^1.4.0",
"react": "^16.2.0",

BTW: I saw someone reporting about the same issue in Stack overflow 1 month ago.
Waiting for a fix of this bug. I want to have textarea in my project.

Code example:

@Ziv-Barber You can find the textfield demo in https://material-ui.com/demos/text-fields/. Your code example is wrong. Either you can an Input inside a FormControl or only use the TextField but not a mix. Also, pay attention to the capitalization of multiline.


typo fix some description error about segcompaction_small_thr…

…eshold
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Support for relative coordinates

It would be useful to be able to choose between absolute pixel coordinates and width/height percentages, specially for use with Wikidata's relative position within image qualifier

+1! Although that would fit the spec only for rectangle shapes. For those, however, it would be fairly easy to implement, if anyone fancies a pull request :-) (Changes would be needed in the RectFragment source file.

my JS skills are still incipient, but now that you pointed to the correct file to modify (which is normally what I spend hours looking for) I'll try and see if I can get it done sometime soon

So, I can add an argument on toRectFragment like
const coordinateMode = {
  Pixel = "pixel"
  Percent = "percent"
}

export const toRectFragment = (x, y, w, h, image, mode) => ({
  const coordinates =
    mode === coordinateMode.Pixel
      ? `xywh=pixel:${x},${y},${w},${h}`
      :  `xywh=percent:${Math.round(x/image.width*100)},${Math.round(y/image.height*100)},${Math.round(w/image.width*100)},${Math.round(h/image.height*100)}`
  source: image?.src,
  selector: {
    type: "FragmentSelector",
    conformsTo: "http://www.w3.org/TR/media-frags/",
    value: coordinates
  }
});

which is a bit ugly IMO, or split the function like
export const toPixelRectFragment = (x, y, w, h, image) => ({
  source: image?.src,
  selector: {
    type: "FragmentSelector",
    conformsTo: "http://www.w3.org/TR/media-frags/",
    value: `xywh=pixel:${x},${y},${w},${h}`
  }
});

export const toPercentRectFragment = (x, y, w, h, image) => ({
  source: image?.src,
  selector: {
    type: "FragmentSelector",
    conformsTo: "http://www.w3.org/TR/media-frags/",
    value: `xywh=percent:${Math.round(x/image.width*100)},${Math.round(y/image.height*100)},${Math.round(w/image.width*100)},${Math.round(h/image.height*100)}`
  }
});

I'm not sure if this image parameter has the dimensions attributes I'm calling, or if they need to come from elsewhere. W3C requires 4 comma-separated integers, so I had to round them despite the Wikidata example above handling floats. Other than that, if this is something you/we want the user to choose when creating annotations, there's an UI element to this issue that is out of my league. Sorry if I completely murdered your code or misunderstood how it works... Let me know if this is along the lines of what you expect, I'll be happy to work on it towards a successful PR :)

Thanks, this looks good! Splitting up the functions is probably a bit more readable. But I don't have strong opinions about that.
Regarding width/height: these need to come from the image naturalWidth and naturalHeight attributes. Width and height describe the size of the HTML image element, and that might be scaled from the original size
Regarding a UI element: I don't think that's necessary. I'd expect the host application to define that, which means an extra init parameter to Annotorious should be enough (something like fragmentCordinates: 'percent'). (Plus: in the first instance, it's already an improvement if Annotorious can read pct fragments. Even if it still would write it pixel coords.)

Thanks again for your PR! I made a few tweaks. Support in AnnotoriousOSD does actually require a handful of (minimal) changes, but I'll take care of that.

Happy to help!


Adding Examples of single event runs

Fixed minor bugs in the test script which could yield nan in Adam optimization and ruin the run.
Added examples of single event runs: GW150914_D.py, GW150914_D_heterodyne.py, GW150914_Pv2.py

Btw, we may want to remove legacy examples either in this PR or another new PR.

I am going to close this PR, and separate it into two new PR.

This PR is replaced by #157 and #154


No such module 'Promises' when building for testing on Xcode 15.0-beta5

Description
We have been using the Firebase iOS SDK for some time in our iOS project. In looking to start using Xcode 15 exclusively, when using current versions of everything (specified below), we see the following issue, using the same Xcode project file:

In Xcode 14.3.1, Build for Running -> builds ok
In Xcode 14.3.1, Build for Testing -> builds ok
In Xcode 15.0-beta5, Build for Running -> builds ok
In Xcode 15.0-beta5, Build for Testing -> fails to build with the following error:

No such module 'Promises in FirebaseSessions at line 21: @_implementationOnly import Promises
We've tried adding the -ld64 other linker flag, cleaning the build and Derived Data folders, as well as removing and re-adding the Firebase package.
Screenshot:

Reproducing the issue
No response
Firebase SDK Version
10.13.0
Xcode Version
15.0 beta 5 (15A5209g)
Installation Method
Swift Package Manager
Firebase Product(s)
All
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

{
  "object": {
    "pins": [
      {
        "package": "abseil",
        "repositoryURL": "https://github.com/google/abseil-cpp-binary.git",
        "state": {
          "branch": null,
          "revision": "bfc0b6f81adc06ce5121eb23f628473638d67c5c",
          "version": "1.2022062300.0"
        }
      },
      {
        "package": "Diagnostics",
        "repositoryURL": "https://github.com/WeTransfer/Diagnostics.git",
        "state": {
          "branch": null,
          "revision": "c3816d37ff6993b7de46aff3370354c4cadca7c8",
          "version": "4.5.0"
        }
      },
      {
        "package": "ExceptionCatcher",
        "repositoryURL": "https://github.com/sindresorhus/ExceptionCatcher",
        "state": {
          "branch": null,
          "revision": "a7acaf40f8bd67a1f3a05a14de5b6a861ac3d1ac",
          "version": "2.0.1"
        }
      },
      {
        "package": "Firebase",
        "repositoryURL": "https://github.com/firebase/firebase-ios-sdk",
        "state": {
          "branch": null,
          "revision": "df2171b0c6afb9e9d4f7e07669d558c510b9f6be",
          "version": "10.13.0"
        }
      },
      {
        "package": "GoogleAppMeasurement",
        "repositoryURL": "https://github.com/google/GoogleAppMeasurement.git",
        "state": {
          "branch": null,
          "revision": "03b9beee1a61f62d32c521e172e192a1663a5e8b",
          "version": "10.13.0"
        }
      },
      {
        "package": "GoogleDataTransport",
        "repositoryURL": "https://github.com/google/GoogleDataTransport.git",
        "state": {
          "branch": null,
          "revision": "aae45a320fd0d11811820335b1eabc8753902a40",
          "version": "9.2.5"
        }
      },
      {
        "package": "GoogleUtilities",
        "repositoryURL": "https://github.com/google/GoogleUtilities.git",
        "state": {
          "branch": null,
          "revision": "c38ce365d77b04a9a300c31061c5227589e5597b",
          "version": "7.11.5"
        }
      },
      {
        "package": "gRPC",
        "repositoryURL": "https://github.com/google/grpc-binary.git",
        "state": {
          "branch": null,
          "revision": "f1b366129d1125be7db83247e003fc333104b569",
          "version": "1.50.2"
        }
      },
      {
        "package": "GTMSessionFetcher",
        "repositoryURL": "https://github.com/google/gtm-session-fetcher.git",
        "state": {
          "branch": null,
          "revision": "d415594121c9e8a4f9d79cecee0965cf35e74dbd",
          "version": "3.1.1"
        }
      },
      {
        "package": "Kingfisher",
        "repositoryURL": "https://github.com/onevcat/Kingfisher.git",
        "state": {
          "branch": null,
          "revision": "c75584ac759cbb16b204d0a7de3ebf53ea6b304d",
          "version": "7.9.0"
        }
      },
      {
        "package": "leveldb",
        "repositoryURL": "https://github.com/firebase/leveldb.git",
        "state": {
          "branch": null,
          "revision": "0706abcc6b0bd9cedfbb015ba840e4a780b5159b",
          "version": "1.22.2"
        }
      },
      {
        "package": "nanopb",
        "repositoryURL": "https://github.com/firebase/nanopb.git",
        "state": {
          "branch": null,
          "revision": "819d0a2173aff699fb8c364b6fb906f7cdb1a692",
          "version": "2.30909.0"
        }
      },
      {
        "package": "Promises",
        "repositoryURL": "https://github.com/google/promises.git",
        "state": {
          "branch": null,
          "revision": "e70e889c0196c76d22759eb50d6a0270ca9f1d9e",
          "version": "2.3.1"
        }
      },
      {
        "package": "RevenueCat",
        "repositoryURL": "https://github.com/RevenueCat/purchases-ios.git",
        "state": {
          "branch": null,
          "revision": "f2f5314fa92d3556fe23e857b34eeed13934c6fb",
          "version": "4.25.2"
        }
      },
      {
        "package": "SFSafeSymbols",
        "repositoryURL": "https://github.com/SFSafeSymbols/SFSafeSymbols",
        "state": {
          "branch": null,
          "revision": "7cca2d60925876b5953a2cf7341cd80fbeac983c",
          "version": "4.1.1"
        }
      },
      {
        "package": "swift-log",
        "repositoryURL": "https://github.com/apple/swift-log.git",
        "state": {
          "branch": null,
          "revision": "32e8d724467f8fe623624570367e3d50c5638e46",
          "version": "1.5.2"
        }
      },
      {
        "package": "SwiftProtobuf",
        "repositoryURL": "https://github.com/apple/swift-protobuf.git",
        "state": {
          "branch": null,
          "revision": "ce20dc083ee485524b802669890291c0d8090170",
          "version": "1.22.1"
        }
      },
      {
        "package": "swiftui-introspect",
        "repositoryURL": "https://github.com/siteline/SwiftUI-Introspect.git",
        "state": {
          "branch": "master",
          "revision": "e93995cb75170a18113ddf1e3cf0d0668c33c8b2",
          "version": null
        }
      },
      {
        "package": "SwiftUIX",
        "repositoryURL": "https://github.com/SwiftUIX/SwiftUIX",
        "state": {
          "branch": null,
          "revision": "75d5be2c85ec1e3ccbd9d99d321dd3abb5955e8d",
          "version": "0.1.6"
        }
      }
    ]
  },
  "version": 1
}

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

@pgorrindo Thanks for the report. Would you check if File -> Packages -> Reset Package Caches makes a difference?

thanks @paulb777 -- tried reseting package caches, same result as originally described.

Hmm, we may need a reproducible example, since I'm able to successfully build Sessions for testing in beta 5.

Here is a reproducible example @paulb777 -- https://github.com/whforward/promises-debugging -- a fresh new Xcode project created with Xcode 15-beta5, bringing in only the current 10.13.0 version of the Firebase SDK, and I get the results as described above.
Greatly appreciate any insight you might have here.

Thanks! I've reproduced and I'm investigating ....

Thanks @paulb777 -- ok, this is what I've found:
recapitulate FirebaseCrashlytics + FirebasePerformance
If I whittle down to just those two, I can reproduce what you see -- Promises error if both Crashlytics and Performance are present:

and then by removing Performance, it builds:

removing FirebasePerformance alone is insufficient
but if I add everything back, and only remove FirebasePerformance, then I get a new error, about undefined symbols in FirebaseFirestoreSwift:

ultimately need to remove all Firestore, and FirebasePerformance
to get past the undefined symbols error, I needed to remove all three Firestore dependencies, and FirebasePerformance, to get be able to successfully Build for Running and Build for Testing:

Thoughts?
You are correct, Paul, that we don't need all of those dependencies for the test target. But we do need Firestore, unfortunately. Thoughts?

Yes, I can reproduce with only FirebaseFirestoreSwift as a dependency of the test target:
ld: Undefined symbols:
  grpc::ClientContext::AddMetadata(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&), referenced from:
      firebase::firestore::remote::FirebaseMetadataProviderApple::UpdateMetadata(grpc::ClientContext&) in FirebaseFirestore[x86_64][74](firebase_metadata_provider_apple.o)
      firebase::firestore::remote::FirebaseMetadataProviderApple::UpdateMetadata(grpc::ClientContext&) in FirebaseFirestore[x86_64][74](firebase_metadata_provider_apple.o)
      firebase::firestore::remote::FirebaseMetadataProviderApple::UpdateMetadata(grpc::ClientContext&) in FirebaseFirestore[x86_64][74](firebase_metadata_provider_apple.o)
      firebase::firestore::remote::GrpcConnection::CreateContext(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateContext(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateContext(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateContext(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateContext(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const in FirebaseFirestore[x86_64][105](grpc_connection.o)
      ...
  grpc::ClientContext::TryCancel(), referenced from:
      firebase::firestore::remote::GrpcStream::Shutdown() in FirebaseFirestore[x86_64][109](grpc_stream.o)
      firebase::firestore::remote::GrpcUnaryCall::Shutdown() in FirebaseFirestore[x86_64][111](grpc_unary_call.o)
  grpc::ClientContext::ClientContext(), referenced from:
      firebase::firestore::remote::GrpcConnection::CreateContext(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::ClientContext::~ClientContext(), referenced from:
      std::__1::unique_ptr<grpc::ClientContext, std::__1::default_delete<grpc::ClientContext>>::~unique_ptr() in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateStream(absl::lts_20220623::string_view, firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, firebase::firestore::remote::GrpcStreamObserver*) in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateStream(absl::lts_20220623::string_view, firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, firebase::firestore::remote::GrpcStreamObserver*) in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateStream(absl::lts_20220623::string_view, firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, firebase::firestore::remote::GrpcStreamObserver*) in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateUnaryCall(absl::lts_20220623::string_view, firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, grpc::ByteBuffer const&) in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateUnaryCall(absl::lts_20220623::string_view, firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, grpc::ByteBuffer const&) in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateUnaryCall(absl::lts_20220623::string_view, firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, grpc::ByteBuffer const&) in FirebaseFirestore[x86_64][105](grpc_connection.o)
      ...
  grpc::SslCredentials(grpc::SslCredentialsOptions const&), referenced from:
      firebase::firestore::remote::(anonymous namespace)::CreateSslCredentials(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::CompletionQueue::AsyncNextInternal(void**, bool*, gpr_timespec), referenced from:
      firebase::firestore::remote::Datastore::PollGrpcQueue() in FirebaseFirestore[x86_64][35](datastore.o)
      firebase::firestore::remote::Datastore::PollGrpcQueue() in FirebaseFirestore[x86_64][35](datastore.o)
  grpc::CompletionQueue::Shutdown(), referenced from:
      firebase::firestore::remote::Datastore::Shutdown() in FirebaseFirestore[x86_64][35](datastore.o)
  grpc::ChannelArguments::SetSslTargetNameOverride(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&), referenced from:
      firebase::firestore::remote::GrpcConnection::CreateChannel() const in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::ChannelArguments::SetInt(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, int), referenced from:
      firebase::firestore::remote::GrpcConnection::CreateChannel() const in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::ChannelArguments::ChannelArguments(), referenced from:
      firebase::firestore::remote::GrpcConnection::CreateChannel() const in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::ChannelArguments::~ChannelArguments(), referenced from:
      firebase::firestore::remote::GrpcConnection::CreateChannel() const in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateChannel() const in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::CreateCustomChannel(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::shared_ptr<grpc::ChannelCredentials> const&, grpc::ChannelArguments const&), referenced from:
      firebase::firestore::remote::GrpcConnection::CreateChannel() const in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateChannel() const in FirebaseFirestore[x86_64][105](grpc_connection.o)
      firebase::firestore::remote::GrpcConnection::CreateChannel() const in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::g_core_codegen_interface, referenced from:
      firebase::firestore::remote::Datastore::PollGrpcQueue() in FirebaseFirestore[x86_64][35](datastore.o)
      firebase::firestore::remote::Datastore::CommitMutationsWithCredentials(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::vector<firebase::firestore::model::Mutation, std::__1::allocator<firebase::firestore::model::Mutation>> const&, std::__1::function<void (firebase::firestore::util::Status const&)>&&) in FirebaseFirestore[x86_64][35](datastore.o)
      firebase::firestore::remote::Datastore::CommitMutationsWithCredentials(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::vector<firebase::firestore::model::Mutation, std::__1::allocator<firebase::firestore::model::Mutation>> const&, std::__1::function<void (firebase::firestore::util::Status const&)>&&) in FirebaseFirestore[x86_64][35](datastore.o)
      firebase::firestore::remote::Datastore::LookupDocumentsWithCredentials(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::vector<firebase::firestore::model::DocumentKey, std::__1::allocator<firebase::firestore::model::DocumentKey>> const&, std::__1::function<void (firebase::firestore::util::StatusOr<std::__1::vector<firebase::firestore::model::Document, std::__1::allocator<firebase::firestore::model::Document>>> const&)>&&) in FirebaseFirestore[x86_64][35](datastore.o)
      firebase::firestore::remote::Datastore::LookupDocumentsWithCredentials(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::vector<firebase::firestore::model::DocumentKey, std::__1::allocator<firebase::firestore::model::DocumentKey>> const&, std::__1::function<void (firebase::firestore::util::StatusOr<std::__1::vector<firebase::firestore::model::Document, std::__1::allocator<firebase::firestore::model::Document>>> const&)>&&) in FirebaseFirestore[x86_64][35](datastore.o)
      firebase::firestore::remote::Datastore::RunAggregateQueryWithCredentials(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, firebase::firestore::core::Query const&, std::__1::vector<firebase::firestore::model::AggregateField, std::__1::allocator<firebase::firestore::model::AggregateField>> const&, std::__1::function<void (firebase::firestore::util::StatusOr<firebase::firestore::model::ObjectValue> const&)>&&) in FirebaseFirestore[x86_64][35](datastore.o)
      firebase::firestore::remote::Datastore::RunAggregateQueryWithCredentials(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, firebase::firestore::core::Query const&, std::__1::vector<firebase::firestore::model::AggregateField, std::__1::allocator<firebase::firestore::model::AggregateField>> const&, std::__1::function<void (firebase::firestore::util::StatusOr<firebase::firestore::model::ObjectValue> const&)>&&) in FirebaseFirestore[x86_64][35](datastore.o)
      ...
  grpc::InsecureChannelCredentials(), referenced from:
      firebase::firestore::remote::GrpcConnection::CreateChannel() const in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::Status::OK, referenced from:
      grpc::SerializationTraits<grpc::ByteBuffer, void>::Deserialize(grpc::ByteBuffer*, grpc::ByteBuffer*) in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::g_glip, referenced from:
      grpc::GrpcLibraryCodegen::GrpcLibraryCodegen(bool) in FirebaseFirestore[x86_64][35](datastore.o)
      grpc::GrpcLibraryCodegen::~GrpcLibraryCodegen() in FirebaseFirestore[x86_64][35](datastore.o)
  grpc::Channel::GetState(bool), referenced from:
      firebase::firestore::remote::GrpcConnection::EnsureActiveStub() in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::Version(), referenced from:
      firebase::firestore::remote::GrpcConnection::CreateContext(firebase::firestore::credentials::AuthToken const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const in FirebaseFirestore[x86_64][105](grpc_connection.o)
  grpc::ByteBuffer::Dump(std::__1::vector<grpc::Slice, std::__1::allocator<grpc::Slice>>*) const, referenced from:
      firebase::firestore::remote::ByteBufferReader::ByteBufferReader(grpc::ByteBuffer const&) in FirebaseFirestore[x86_64][106](grpc_nanopb.o)
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Seems to be some sort of C++ symbol or linkage problem. I'm not sure why it only shows up in the test target. @ncooke3 any ideas?

Beta 6 makes no difference on the Firestore grpc linkage problem.

Hi @pgorrindo, I unfortunately don't have any advice to work around this issue at this time. We'll keep this open to verify against the issue against future betas.

Hi @pgorrindo, I unfortunately don't have any advice to work around this issue at this time. We'll keep this open to verify against the issue against future betas.

bummer, ok thanks for the update @ncooke3
CC @andrewsexcellent

Beta 6 makes no difference on the Firestore grpc linkage problem.

Same with Xcode 15 Betas 7 and 8, and Firebase v10.14.0 -- the problem persists.

Same with Xcode 15 Release Candidate, and Firebase v10.15.0 -- the problem persists in the minimal reproducible example previously noted. Trying -ld64 or -ld_classic as other linker flags doesn't fix the issue either. Any other thoughts @ncooke3 or @paulb777 ? CC @andrewsexcellent

Yep. I still see the C++ linkage issue from Firestore with the Xcode 15 RC.  The original issue reported here of not being able to add both Crashlytics and Performance to the test target has been addressed.
I suspect something about the Xcode 14 generated binary for Firestore may be missing something needed by Xcode 15. We'll continue to investigate.

Hi @pgorrindo, we identified a fix for the undefined symbols errors. The fix should go out in the next release.
Until then, I have a manual workaround that can help unblock your workflow.

Find the Process FirebaseFirestore.xcframework step in a build log. This should appear whenever building a target that depends on Firestore.

Copy the path of the xcframework being processed. In my case, it's the following path from the above image:

/Users/nickcooke/Library/Developer/Xcode/DerivedData/testApp1-gplcekzwfpjbfyendznnuavepyqs/SourcePackages/artifacts/firebase-ios-sdk/FirebaseFirestore/FirebaseFirestore.xcframework

The FirebaseFirestore.xcframework contains a directory for each supported architecture slice. Within each slice is a  FirebaseFirestore.framework. For each of the architectures you build for, find the module.modulemap within the  architecture's corresponding FirebaseFirestore.framework.

For me, the module.modulemap used when building your repro project is here:
/Users/nickcooke/Library/Developer/Xcode/DerivedData/testApp1-gplcekzwfpjbfyendznnuavepyqs/SourcePackages/artifacts/firebase-ios-sdk/FirebaseFirestore/FirebaseFirestore.xcframework/ios-arm64_x86_64-simulator/FirebaseFirestore.framework/Modules/module.modulemap

Then, open the module.modulemap in a text , vim, etc. and it should look like:
framework module FirebaseFirestore {
umbrella header "FirebaseFirestore-umbrella.h"
export *
module * { export * }
  link framework "Foundation"
  link framework "Security"
  link framework "SystemConfiguration"
  link framework "UIKit"
  link "c++"
  link "z"
}

Link in BoringSSL-GRPC, gRPC-Core, and gRPC-C++ so it looks like this:
framework module FirebaseFirestore {
umbrella header "FirebaseFirestore-umbrella.h"
export *
module * { export * }
  link framework "BoringSSL-GRPC"
  link framework "gRPC-Core"
  link framework "gRPC-C++"
  link framework "Foundation"
  link framework "Security"
  link framework "SystemConfiguration"
  link framework "UIKit"
  link "c++"
  link "z"
}

Repeat this last step for each of the architectures you wish to build for.
Try building your target again, and it should work with the locally modified artifact.

You will need to repeat these steps if the DerivedData directory is deleted, or if you re-add Firebase via SPM.
Let me know if you have any trouble.

woohoo, thanks @ncooke3 and @paulb777 !! 🎉


Disable biomes

Is there a way to disable biomes from generating in Terraforged? If so, how?

Not in current release versions. The beta has a system for setting biome weights in a config file which may work depending on the biome (some biomes act as a default for certain conditions so can't be 'disabled' entirely)


Placing single slab on single slab should make a double slab

Not sure if we can fix this easily

Completed in https://github.com/telvarost/AnnoyanceFix-StationAPI/commit/71bf994e0ea63ef8461215e3c758e012f997535e


ADD link to operations handout

Added missing link on top of page to operations handout.

Depends on #135


Adapt to new Indico 3.3 design system

Indico 3.3 has made some adaptions that give us more CSS variables. Also, as a result, there are some theme differences we need to adapt to. Indico 3.3 will be release soon (tm), and if soon enough I'd like to get this deployed well before Madrid. Varshi is aware and ready to deploy once it is out.
For that we'd need someone to look at the changes and make sure everything is well, and maybe change some of our overrides to use variables instead.
See
https://github.com/indico/indico/blob/master/indico/web/client/styles/design_system/README.md
https://github.com/indico/indico/blob/master/indico/web/client/styles/design_system/variables.scss
@petesfrench @akbarkz can you introduce this into your planning?

@kewisch the work on this task has been planned for the Pulse that ends March 22nd.


Image picker when using multiple pictures, you can add the parameters to specify the maximum number of pictures can be selected。

Use case

Proposal

Hi @carson2440, can you please provide more information on the issue you have with image picker plugin? Also,
can you please provide your flutter doctor -v and a minimal complete reproducible code sample?
Thank you

i want to select six or another number of images at most，don't find the api to support;
my code :
//i want to select six images at most，don't find api
ImagePicker picker = new ImagePicker();
List? files = await picker.pickMultiImage(maxWidth: 720, maxHeight: 720);
files!.forEach((element) {
_photoPath = element.path;
_imageAddWaterMask(element.path);
});
can you support this api:      List? files = await picker.pickMultiImage(maxImages:6, maxWidth: 720, maxHeight: 720);  the number of images can be selected is maxImages = 6

Hi @carson2440, image_picker does not provide an api to limit the number of images nor it is possible to implement on android due to some limitations please see this comment for more details


Pass pin assignments into constructor

Implemented using a class to hold the associated memory-mapped definitions:
b06052d9a8b59959dfac9ba0a365cd32fd2b40d8


Completing the build...?

My apologies for this new message as it doesn't necessarily fit into the general discussion of making this project better.  I'm relatively new to github and importing code into ubuntu.  I only bring this up here because I am in charge of getting this up an running for my university chemistry department and some responsibility to complete everything (as opposed to giving up if it was a personal system! :) ).
Anyways, I am running Ubuntu 18.04 on a Raspberry Pi 4.  I was able to successfully add the GCC/C++14, CMake, and Qt packages to ubuntu.   For the last ~4 hours I have been trying to complete the "make" portion of the build.  I get a "Fatal error: GLES3/gl31.h: No such file or directory"... etc
After quite a bit of searching, I have installed several libraries, including what I believe to be the correct one - namely the libgles2-mesa-dev library.  I have installed several others along the way that were hinted at, including other mesa utility packages, etc.  Seeing how I am missing the openGL files, I searched on my system for the folders, which didn't seem to be installed after the apt-get installs.  I have tried to install this package several times.  I have also tried to copy the /GLES3/ folder to /opt/vc/ directory to try to force it in there.  That idea came from https://raspberrypi.stackexchange.com/questions/56137/fatal-error-gles2-gl2-h-no-such-file-or-directory.
I'm sort of lost if this is something that is a library that is not installed, or if it is somehow in the compiler code that is leading me astray.   There doesn't seem to be too many google results for the GLES3 issues...   Here is the full error: https://imgur.com/a/53KBky3
Thanks for any input anyone might have.

In this case I only can can resort to a web search too. But basically you are looking to build an application that is using Qt5 (widgets+qml) on a Raspberry Pi.
This might help: https://stackoverflow.com/questions/14184542/qt-creator-qtgui-include-error
sudo apt-get install mesa-common-dev
sudo apt-get install libgl1-mesa-dev libglu1-mesa-dev

@nineinchplate Is your issue resolved?

Closing due to inactivity.


where is the requirements.txt for this?

open the terminal on the ComfyUI/custom_nodes/AILab_OmniGen folder
......\python_embeded\python.exe -m pip install -r requirements.txt
there are no requirements as there is no AILab_omnigen folder and hence no requirements.txt!!!!

it should be  ComfyUI/custom_nodes/ComfyUI-OmniGen


Error when sourcing

Error Message
/usr/local/bin/shml:360: = not found

Line 358 - 365
# Usage / Examples
##
if [ "$0" == "$BASH_SOURCE" ]; then

if [[ $@ =~ .*-v.* ]]; then
  echo "shml version ${SHML_VERSION}"
  exit 0
fi

@voyga weird. How did you install shml?

@Voyga (cc @jdorfman) Though testing, I'm seeing that the == method of testing strings doesn't work in zsh. Can you provide some information by running the following commands and pasting your output to assist me in confirming...
First, shell information:
$SHELL --version

Second, test the line in question alone:
if [ "foo" == "foo" ]; then echo "pass"; else echo "fail"; fi

Lastly, help me test a fix by running:
if [ "foo" = "foo" ]; then echo "pass"; else echo "fail"; fi

All that said, I'm not sure we want to (fully) support zsh, but I'm willing to make a few quick fixes and see if we can get it working.

Upon further inspection (it only took a minute), we're not going to support shells outside of bash at this time.
Ensure that you're running your script though bash by including #!/usr/bin/env bash or #!/bin/bash as the first line of the file,  or by running it like so bash ./your_script.sh.
I'll leave this open for now, awaiting the requested information to ensure that my assumption is correct. Cheers!

Thanks @jmervine

Solved, Thanks. @jmervine

@Voyga Mind clarifying what the issue was you were having in case someone else runs in to the same issue and comes across this thread in a search?
Thanks!
J
PS - Closing

I know this is super old, but when trying to source this in zsh I just had to remove the second = in line 360, and it works fine.
if [ "$0" = "$BASH_SOURCE" ]; then

@simoniz0r thanks for the report. @jmervine I think it is time for a release. Maybe fix this and release #32
LMK and I will start the docs.

Revisiting based on @simoniz0r 's comment.

Addressed on the following commit -- https://github.com/odb/shml/pull/32/commits/cd551bf9762c94032c17aecb0b090fc1fa27ec08


Separate plasma from sync

This PR separates the plasma generation status from the connected/synced status by adding an extra icon to the tab navigation bar.

Below an overview of the different states when syrius is connected/synced and generating plasma.
Currently the syncing icon looks too big in comparison and the connected animation is distracting.

Changed the connection icon to use the CircularProgressIndicator.
Below an example of how this looks in the various states.


Fix slurm-gcp-sync.py

Currently, the slurm-gcp-sync.py script deletes all nodes that are active in GCP's compute engine list.
Issue reported on slurm-gcp google discussion group

Issue resolved and preemptible support with multiple partitions available


feat(runtime): Initial async texture loading across platforms

Experiment with loading an asset directly from bundle
More experiments
Initial async loading of textures

#28  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tommy-xr and the rest of your teammates on  Graphite


update response formatting interceptor

@Savio629 to make the discussed changes.
Changes were:

[ ] remove the top level message key
[ ] remove teh code key from error
[ ] data key should be the response of the service not the body of the POST request.

@ GET('/')

@ POST('/')

@ POST('/') - with a error

@techsavvyash has tested and updated this and will be merged to main for the next release.


Fix rest_framework_jwt can not return the correct UserProfile.

Fixed #290 rest_framework_jwt can not return the correct UserProfile object by adding customized payload_handler. we need to configure JWT_AUTH on settings.py
'JWT_PAYLOAD_GET_USERNAME_HANDLER': 'api.utils.customized_jwt_handlers.jwt_get_user_id_from_payload_handler',

Signed-off-by: Yuanmao Zhu<EMAIL_ADDRESS>

Solve this problem by controlling the uniqueness of user name; E.g. email


How to use ApplyAdam(C++API)?

Hi, I has used C++ API, but I got some problem about ApplyAdam:
ApplyAdam(const ::tensorflow::Scope& scope, ::tensorflow::Input var,
::tensorflow::Input m, ::tensorflow::Input v, ::tensorflow::Input
beta1_power, ::tensorflow::Input beta2_power, ::tensorflow::Input lr,
::tensorflow::Input beta1, ::tensorflow::Input beta2,
::tensorflow::Input epsilon, ::tensorflow::Input grad);
I do not know beta1_power and beta2_power in adam optimizer.

@minjac
Could you please share a simple standalone code to replicate the issue faced by you in our local,along with the tensor flow version.

@minjac
Could you please share a simple standalone code to replicate the issue faced by you in our local,along with the tensor flow version.

Hi, code is doesn't matter in this case, because I just don't know what the beta1_power and beta2_power mean.
/// Update '*var' according to the Adam algorithm. /// /// $$lr_t := \text{learning\_rate} * \sqrt{1 - beta_2^t} / (1 - beta_1^t)$$ /// $$m_t := beta_1 * m_{t-1} + (1 - beta_1) * g$$ /// $$v_t := beta_2 * v_{t-1} + (1 - beta_2) * g * g$$ /// $$variable := variable - lr_t * m_t / (\sqrt{v_t} + \epsilon)$$ /// /// Arguments: /// * scope: A Scope object /// * var: Should be from a Variable(). /// * m: Should be from a Variable(). /// * v: Should be from a Variable(). /// * beta1_power: Must be a scalar. /// * beta2_power: Must be a scalar. /// * lr: Scaling factor. Must be a scalar. /// * beta1: Momentum factor. Must be a scalar. /// * beta2: Momentum factor. Must be a scalar. /// * epsilon: Ridge term. Must be a scalar. /// * grad: The gradient.
As the comments says, I know all the arguments mean except the beta1_power and beta2_power, because I don't find where the beta1_power and beta2_power are in the Adam Optimizer's formula.

@minjac
can you please refer to this link and let us know if it helps

@minjac
can you please refer to this link and let us know if it helps
Thanks for your help, but I cannot find some arguments as same as beta1_power or beta2_power in this API.

@minjac
here is some info on the variables,with reference to your question "Hi, code doesn't matter in this case, because I just don't know what the beta1_power and beta2_power mean."
The beta-variables are variables used by the AdamOptimizer that need to be initialized similarily to your other variables. You can either initialize them with the tf.global_variables_initializer() after creating the optimizer, or look up the variables and initialize them directly with tf.variables_initializer().
here are few links related to them link1 link2
please let us know if this helps.

@minjac
please update on the above comment

@minjac
please update on the above comment

Hi, thanks for reply. I click your link, beta1_power and beta2_power seems to be the same as t in Adam Optimizer's formula.

From https://arxiv.org/pdf/1412.6980.pdf beta1, beta2 are exponential decay rates for the moment estimates.
(default values are set as β1 = 0.9, β2 = 0.999)
https://github.com/tensorflow/tensorflow/blob/e5bf8de410005de06a7ff5393fafdf832ef1d4ad/tensorflow/python/keras/optimizer_v2/adam.py#L48

From https://arxiv.org/pdf/1412.6980.pdf beta1, beta2 are exponential decay rates for the moment estimates.
(default values are set as β1 = 0.9, β2 = 0.999)
https://github.com/tensorflow/tensorflow/blob/e5bf8de410005de06a7ff5393fafdf832ef1d4ad/tensorflow/python/keras/optimizer_v2/adam.py#L51

Thanks for reply, beta_2 seems to be the same as beta1 which in my question.

This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.
Thanks!


package embed: unrecognized import path "embed" (import path does not begin with hostname)

When I run:
go get -u suah.dev/widdler

I get:

package embed: unrecognized import path "embed" (import path does not begin with hostname)

Hi, what version of Go do you have installed? Widdler needs at lest 1.16 (which is when embed was added).

Thanks, I'm using 1.13 on ubuntu 20.04, but I will upgrade

If you upgrade to Go 1.17 you will also need to use "install" vs "get": go install suah.dev/widdler@latest

It seems ya have it running now - I am gonna close this :D


trino admins group cannot drop tables

A while ago I created a few tables as user erik, but have since moved to the more correct github-based erikerlandson account.
However, although in theory erikerlandson has privileges for admins group, I cannot delete this old table created by user erik:
cur.execute('drop table if exists osc_datacommons_dev.urgentem.itr_emissions_1')
cur.fetchall()

results in following error:
TrinoUserError: TrinoUserError(type=USER_ERROR, name=PERMISSION_DENIED,
message="Access Denied: Cannot drop table urgentem.itr_emissions_1:
Owner of the table ('erik') is different from session user ('erikerlandson')",
query_id=20211008_221126_02852_8347x)

I believe we need to configure the admins group to also include ability to drop tables.
cc @rimolive @HumairAK @caldeirav @MichaelTiemannOSC

side-note, I also tried as user admin, but that also errored out:
TrinoUserError(type=USER_ERROR, name=PERMISSION_DENIED,
message="Access Denied: Cannot drop table urgentem.itr_emissions_1:
Owner of the table ('erik') is different from session user ('admin')", query_id=20211008_222513_02853_8347x)

May require somehow assigning the role admin to admins. I haven't figure out where or how role assignments get configured.
https://trino.io/docs/current/connector/hive-security.html#sql-standard-based-authorization


clean up BIO_printf formatting strings.

See the comments in #3044  We should get rid of OSSLzu, etc., and just use our own platform-neutral formatting.

See the comments in #3044 We should get rid of OSSLzu

??? Where does it say that? It says that we should implement 'z' in BIO_printf (so that BIO_printf calls can be used without OSSLzu), and that we should be able to omit PRIu64 (because it's used only with BIO_printf). It also says that OSSLzu is effectively mis-defined in some cases, but it doesn't actually spell that we can get rid of OSSLzu. Well, one can say that it's implied... But if we aim for that, we also have to recognize that in such case we would have to convert all [f]printf calls with OSSLzu to BIO_printf calls...

Hmm, PRIu64 is used as argument in BIO_printf calls, but BIO_printf implements
simply l=long ll=LLONG, you should simply use %llu if it is a LLONG
which is not necessarily int64_t ?

Hmm, PRIu64 is used as argument in BIO_printf calls

Exactly. See #3083.

And after #3094 this can be closed...


Are you going to take over "biesbjerg/ngx-translate-extract-marker" too?

Thank you for taking over the library from biesbjerg.
He also made a second library, which provides a marker to directly extract translations from a component by decorating it with a marker.
--> https://github.com/biesbjerg/ngx-translate-extract-marker
This library did not receive any updates in three years too, seems to be working fine, but is still based on View Engine. This results in a warning when installing it:
Processing legacy "View Engine" libraries:
- @biesbjerg/ngx-translate-extract-marker [es2015/esm2015] (https://github.com/biesbjerg/ngx-translate-extract-marker.git)

Are there any plans to take over this library too?

the way it was designed, the extract-marker is just a no-op that has absolutely 0 lines of logic
https://github.com/biesbjerg/ngx-translate-extract-marker/blob/a02c29f0e2ff6b99073deb32de8673bee20dd7e5/projects/ngx-translate-extract-marker/src/lib/ngx-translate-extract-marker.ts#L1-3
what ngx-translate-extract does is parsing your code, looking for import statement that import a module named 'SOMETHING/ngx-extract-translate-marker' (and SOMETHING before the slash is irrelevant , it can be anything)  and detect where the marker imported from this library is used .
There is nothing to maintain in the marker repository, all the logic is in this (current) respository. and will work the the biesbjerg marker package.

Thanks @colsen1991 will be using your version until the situation is clear

Hi chaps,
I'm really sorry - I had failed to set up notifications for this repo 🤦 so I wasn't aware of the activity here. A dropped ball for sure given the circumstances of this fork!
In any case, now I'm making my way through the PRs and will issue a new version today.

OK v8.0.5 is out now.
And this got me thinking - why is the marker function a separate package anyway? Is it because one is a dev dependency and the other is a regular dependency?
It seems an awful lot of overhead for what is essentially an identity function. What's a better way to do this? Open to suggestions here but in general my bias is to reduce dependencies wherever possible. Better for the consumers and maintainers!

@michaelbromley I don't know the history of the marker lib, but @tmijieux brings up a good point regarding tree shaking and the two libs being very different in terms of dev and runtime dependency.  So i suggest the two libs stay separate. Also given that not everyone who uses extract needs the marker fn as extract also works with translate fn, pipe and directive.
So I suggest that either:

@colsen1991/ngx-translate-extract-marker lives on (BTW, soon to be @husbanken/ngx-translate-extract-marker) as a standalone lib and I update my PR to redirect to it instead of @biesbjerg's marker lib
or that you (Vendure) fork my fork of marker fn with its improvements and take over future maintanance

From what I can tell marker is just a no-op and I don't see many changes being introduced there in the future, especially since my fork now supports custom marker fn with the --marker and -m option. and a marker directive and pipe.
Either way I will update my PR to this repo to include the other improvents introduced in my fork, mark my fork as deprecated, redirect to yours (@vendure/ngx-translate-extract) and discontinue publishing it. Although I'll leave the published versions up on NPM for anyone who's added it as a dependency.
What do you guys think?

Hi @colsen1991
Long-term, I guess it makes sense for the extract & marker libs to both live in the Vendure org. Right now I don't want to hold up your work on your PR so I'd say we can leave it pointing to the husbanken version until I have a spare moment to fork and set up a new npm package.
I'm also interested in at some point exploring the proposal of @tmijieux about an API for a custom extract function.

I'm also interested in at some point exploring the proposal of @tmijieux about an API for a custom extract function.

you can try it out at npm @colsen1991/ngx-translate-extract (or @aum_biosync/ngx-translate-extract)
old commit from Biesbjerg that originally introduced the feature:
https://github.com/Husbanken/ngx-translate-extract/commit/bc5ce7e80d67192105260568b97618926558779f
https://github.com/Husbanken/ngx-translate-extract/commit/daaebede6f78d724ed66228d4d33b7e30444547b
commit that removed it:
https://github.com/Husbanken/ngx-translate-extract/commit/4fe3c436244335fcb7ade90786eecf001314c7db
commit where i re-introduce it:
https://github.com/Husbanken/ngx-translate-extract/commit/f8d1279c1e84de24a49926fa08043627a1d7e970

@michaelbromley yeah, makes sense for them to coexist under the same namespace, so let's talk after I've updated my PR (I'll let you know once its ready) and it has been merged and published.
And as @tmijieux mentioned the custom marker function has already been re-implemented in my fork, so if you want to test it out just follow his instructions. I'll look into including this option in the PR if you want?

@michaelbromley just updated the PR. Sorry for the mess, but I hoep you'll be able to parse/power through it :)
Also as mentioned there, I'm gonna prep a branch on my fork of ngx-translate-extract-marker to make it easier for you to take over that lib as well.

@michaelbromley branch for marker lib should be ready: https://github.com/Husbanken/ngx-translate-extract-marker/tree/chore/move-to-vendure-ecommerce :)

@colsen1991 I see you created the fork but the librarary "@vendure/ngx-translate-extract-marker" is not released yet, isn't it?

No worries, @michaelbromley! And no, it's not published yet - I only created the branch to accomodate Vendure taking over :) So it should just be fork, merge, code review and publish on your end 👍

Can I somehow help you with it?

@colsen1991 thanks for prepping things like that, makes my life much easier :)
@StefanKern my ideal setup would not be to have 2 separate git repos, but to have the marker package also published from this repo, making this a monorepo to keep everything together. If that is something you are interested in helping with, let me know and I'll make you a maintainer so you can work on that independently of me. If not, I will just form Christer's repo for now and publish from there.

So you would like to merge the code into a single repository and publish both libraries from here? I would like to take a look at it in the next days and maybe I can be of help :)
PS: Grüße aus Wien zurück :)

Hey, I thought this would be a quick change, but then also did not really have the time for it. Also I'm no longer convinced it would be a good idea. ngx-translate-extract and ngx-translate-extract-marker  user very different technologies. Merging them together then creates a pretty large package.json and makes the generation of the two packages more complex.
So after trying it out for way to long, I would keep the two projects.

With the recent release of ngx-translate@16, the core library now includes a built-in marker function:
Migration Guide - Using the ngx-translate-_-marker Function.
I suggest updating the documentation point to this direction. For simple use cases, the built-in marker function can be highlighted as the preferred approach. For more advanced scenarios where a marker pipe or directive is required, the documentation could still reference the implementation by @colsen1991.


Is it possible to redefine cluster overlap?

I've redefine onBeforeClusterItemRendered and onBeforeClusterRendered as on Image.
I want Cluster [2 items] has Marker 2 because cluster partly overlap marker.
Marker and Cluster created via LayoutInflater and converted to Bitmap.
TestRender r = new TestRender(activity, clusterManager, map);
r.setMinClusterSize(1);

clusterManager.addItems(pins);
clusterManager.setRenderer(r);

Is it possible to redefine cluster overlap?

Found solution in Algorithm interface.


iPad support

Image browser shows an empty center column when run on an iPad.
Edit: Only seems to be a problem when running with 3 items per row.

Thank you for your investigation! I will look into it whenever I have time!


Update node version to 20.16.0

Description
Updating node to latest LTS - v20.16.0
Checklist

[ ] Code compiles correctly
[ ] Relevant tests were added (unit / contract / integration)
[ ] Relevant logs were added
[ ] Formatting and linting run locally successfully
[ ] All tests pass
[ ] UA review
[ ] Design is documented
[ ] Extended the README / documentation, if necessary
[ ] Open source is approved

from Makarenko, Alexander
Hello! Hope I'm not disturbing you for no reason. But as I see you are a code owner of
https://github.com/SAP/cloud-mta-build-tool/
. There is a PR
https://github.com/SAP/cloud-mta-build-tool/pull/1124
that is very anticipated to be merged. Me and a some other people in SAP are a little bit blocked with the Node version provided by
https://hub.docker.com/r/devxci/mbtci-java17-node20
. So this PR updates node version to the latest LTS. Can you please review and merge? Thanks a lot


Fix linker option for noexecstack

Zero length PT will now be supported by new algorithm called AES-GMAC.


Add slack integration module to paraply

It would be cool to have Slack-integration for Paraply. Essentially the paraply node application would contact the Slack service upon receiving new events and post them in the specified room.
The integration part should be fairly trivial. The hard part, as the server is designed now, is determining whether the event being added to the db is actually new, or just an update.
Another possibility is finishing the api and create a slack command to list the first upcoming events in the chat room.

Any updates on this Torthu?

Not yet, @Snorremd. We still need to solve the updated vs new problem.


No hologram, non-removable armor stands.

SethBling's heaven.

According to plugin.yml, I'm using ShopChest 1.12.3.
Server version: git-Paper-118 (MC: 1.15.2)
A piece of log:
[INFO] .... AmadeusDream issued server command: /shop create 1 0 10
[ERROR] .... [ShopChest] Failed to create line for hologram
[ERROR] .... [ShopChest] Failed to create line for hologram
[ERROR] .... [ShopChest] Failed to create line for hologram
[ERROR] .... [ShopChest] Failed to create line for hologram
[ERROR] .... [ShopChest] Failed to create shop item
[INFO] .... AmadeusDream issued server command: /shop remove
[ERROR] .... [ShopChest] Could not remove hologram
[ERROR] .... [ShopChest] Could not remove hologram
[ERROR] .... [ShopChest] Could not remove hologram
[ERROR] .... [ShopChest] Could not remove hologram

Every reload, right after "Done!":
[ShopChest] Plugin ShopChest v1.12.3 generated an exception while executing task 20
java.lang.NullPointerException: null
at de.epiceric.shopchest.utils.UpdateChecker.check(UpdateChecker.java:43) ~[?:?]
at de.epiceric.shopchest.ShopChest$4.run(ShopChest.java:321) ~[?:?]
at org.bukkit.craftbukkit.v1_15_R1.scheduler.CraftTask.run(CraftTask.java:84) ~[patched_1.15.2.jar:git-Paper-120]
at org.bukkit.craftbukkit.v1_15_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:54) ~[patched_1.15.2.jar:git-Paper-120]
at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22) ~[patched_1.15.2.jar:git-Paper-120]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_212]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_212]
at java.lang.Thread.run(Thread.java:813) [?:1.8.0_212]

Ooops, sorry. My mistake. Switched to dev build and it seems no issues here.


CRI: An empty DNSConfig != unspecified

If we find that DNSConfig is provided and empty (not nil), we should not replace it with the host's resolv.conf.
Also adds tests.

There's a cherry pick label for 1.6.x but missing from release/1.6 branch...


KAFKA-8299: Add generic-safe getConfiguredInstance() methods to AbstractConfig

Jira
The changes here add four new methods to the AbstractConfig class that mirror the existing getConfiguredInstance(...) and getConfiguredInstances(...) methods; the only difference is that any parameter of type Class<T> is changed to TypeLiteral<T> and that type checking is done with TypeUtils.isInstance(...) instead of Class.isInstance(...)
A new unit test (AbstractConfigTest.testGenericClassInstantiation()) confirms this behavior, including the lack of unchecked cast warnings and the throwing of a runtime exception when an attempt is made to instantiate a class that extends from/implements the proper raw type but with improper type parameters.
Committer Checklist (excluded from commit message)

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

Copied directly from the Jira:

Since this affects public API it's possible a KIP will be required, but the changes are pretty lightweight (four new methods that heavily resemble existing ones). If a contributor or committer, especially one familiar with this section of the codebase, has an opinion on the necessity of a KIP their input would be appreciated.

Closing as I have no plans to work on this any time in the near future.


Recognition of Matoniales

Author(s) of proposal
Jiang-Ping Shu
Name of taxon
Matoniales
Rank of taxon
Order
Approximate number of species affected
15
Description of change
Recognition of the order Matoniales composed of two families Dipteridaceae (including Cheiropleuria and Dipteris) and Matoniaceae (including Matonia and Phanerosorus), with a total of 15 species.
Reason for change
In PPGI (2016) and Smith et al. 2006, Matoniales was treated as the synonym of Gleicheniales (including Gleicheniaceae, Matoniaceae, Dipteridaceae). However, several phylogenomic studies (Shen et al. 2018; Qi et al. 2018; Du et al. 2022; Shu et al. 2022; Pelosi et al. 2022) revealed that Gleicheniales was a paraphyletic group, but Matoniaceae and Dipteridaceae were a monophyletic group. Therefore, Shu et al. 2022 proposed to redefine a general ordinal rank of Matoniales from Dipteridales Doweld (2001) and Matoniales Reveal (1993) based on the cre International Code of Nomenclature for algae, fungi, and plants (Shenzhen Code).
Phylogenetically, Matoniales is a monophyletic group, composed of Dipteridaceae (including Cheiropleuria and Dipteris) and Matoniaceae (Matonia and Phanerosorus), with a total of 15 species. Morphologically, the species in Matoniales share a number of common morphological characters, such as a creeping rhizome, dichotomous or fan-like split leaves, and flattened sporangia with slightly oblique or sub-erected annulus; they are more or less similar in their spore morphologies (sub-triangular or elliptisoidal spore shape with trilete marks or monolete), and they are mainly distributed in tropical regions in Asia, extending to China and Japan.
Reference(s) for publication of the name
Shu J-P, Wang H, Shen H, Wang R-J, Fu Q, Wang Y-D, Jiao Y-N, Yan Y-H (2022). Phylogenomic Analysis Reconstructed the Order Matoniales from Paleopolyploidy Veil. Plants 11(12): 1529. https://doi.org/10.3390/plants11121529
Reveal, J. New ordinal names for extant vascular plants. Phytologia 1993, 74, 173–177.
Shen H, Jin D, Shu J-P, Zhou X-L, Lei M, Wei R, Shang H, Wei H-J, Zhang R, Liu L, Gu Y-F, Zhang X-C, Yan Y-H (2018). Large-scale phylogenomic analysis resolves a backbone phylogeny in ferns. GigaScience 7(2): 1-11. https://doi.org/10.1093/gigascience/gix116.
Qi, X., Kuo, L-Y., Gou, C., Li, H., Li, Z., Qi, J., Wang, L., Hu, Y., Xiang, J., Zhang, C., Guo, J., H., C-H., and Ma., H. 2018. A well-resolved fern nuclear phylogeny reveals the evolution history of numerous transcription factor families. Molecular Phylogenetics and Evolution 127: 961-977. https://doi.org/10.1016/j.ympev.2018.06.043
Du, X-Y., Kuo, L-Y., Zuo, Z-Y., Li, D-Z., Lu, J-M. 2022. Structural variation of plastomes provides key insight into the deep phylogeny of ferns. Frontiers in Plant Science 13:862772. https://doi.org/10.3389/fpls.2022.862772
Pelosi, J.A., Kim, E.H., Barbazuk, W.B., and Sessa, E.B. 2022. Phylotranscriptomics illuminates the placement of whole genome duplications and gene retention in ferns. Frontiers in Plant Science. 13:882441. https://doi.org/10.3389/fpls.2022.882441
List the numbers of any related issues
No response
Code of Conduct

[X] I agree to follow the PPG Code of Conduct

I think that this proposal is very interesting and goes beyond what PPG I proposes in light of the new molecular evidence about the paraphilia of Gleicheniales. However, I also think that the morphological characters cited therein are not entirely appropriate since most of them are also shared with Gleicheniaceae (e. g. species in Gleicheniaceae also have creeping rhizomes, trilete spores, dichotomous leaves, sporangia with a slightly oblique annulus). Therefore, these characters would not make it possible to distinguish Gleicheniales from Matoniales and, if they remain so in the final version of the article, they could cause confusion in the inexperienced reader. What do you think?


LOG4J2-3538 Added support for 24 colors in highlighting

My first pull request. Please, check.

@ppkarwasz Could you take a look why it failed? It seems the problem is that we added event logging for exception.


Ollama API documentation should contain the default values for API options.

As a developer, I want to know the default values Ollama uses for API request options so that I can create reproducible API calls between different kinds of clients.
Some AI libraries provide default values for options that are different from those used by the Ollama API. I want to override the library's default value with the Ollama default value.
I understand I will also need to check the modelfile, but if the modelfile does not specify a value, it will use what Ollama uses.
The https://github.com/ollama/ollama/blob/main/docs/modelfile.md#valid-parameters-and-values lists the options but with an example, which I don't assume may not represent the default value.

I agree it could be easier. There are some default values in that list at the end of the descriptions. However i'm not seeing all the same options in api.md to whats in modelfile.md.