[CT-1912] [Regression] require_partition_filter usage with insert_overwrite fails on second run

Is this a regression in a recent version of dbt-bigquery?

[X] I believe this is a regression in dbt-bigquery functionality
[X] I have searched the existing issues, and I could not find an existing issue for this regression

Current Behavior
Let's take this simple example:
{{
    config(
        materialized = 'incremental',
        incremental_strategy='insert_overwrite',
        partition_by = {
          "field": "hour",
          "data_type": "timestamp",
          "granularity": "hour"
        },
        require_partition_filter = true,
    )
}}
SELECT TIMESTAMP('2023-01-25') as hour, 1 as value

If you run it twice it will fail with "Query error: Cannot query over table '<project>.<dataset>.test_bug' without a filter over column(s) 'hour' that can be used for partition elimination at [39:5]"
Expected/Previous Behavior
The query should be successful.
Steps To Reproduce
Using dbt-bigquery 1.4.0rc1 (or any 1.4.0)
Why it fails?
Because the generated code is the following
...
when not matched by source
         and timestamp(timestamp_trunc(DBT_INTERNAL_DEST.hour, hour)) in unnest(dbt_partitions_for_replacement)
        then delete
...

instead of
...
when not matched by source
         and timestamp_trunc(DBT_INTERNAL_DEST.hour, hour) in unnest(dbt_partitions_for_replacement)
        then delete
...

The reason is that BigQuery can't figure out timestamp(timestamp_trunc(DBT_INTERNAL_DEST.hour, hour)) is the same as timestamp_trunc(DBT_INTERNAL_DEST.hour, hour) which means it can't forward the origin of the field (hour) to the resulting recreated field. Though we could expect the query planner to do job of inline (and prune) the timestamp cast... it's not the case so we'll have to be smarter when we generate the query to not include it.
Relevant log output
No response
Environment
- OS:Mac 12.6
- Python: 3.10.9
- dbt-core (working version):1.3.2
- dbt-bigquery (working version): 1.3.0
- dbt-core (regression version): 1.4.0-X
- dbt-bigquery (regression version): 1.4.0-X

Additional Context
No response

Hello @dbeatty10,
Thanks for looking at it.
I don't think it works in all cases, I think we need to improve the coverage because depending on the partitioning type I'm not sure it would work.
Also I think it doesn't work for instance, with 'data_type': 'date' because we should use _PARTITIONDATE instead _PARTITIONTIME for the create table query but let's keep it for another issue 😅

Big +1 to this. We upgraded to dbt-bigquery==1.4.0 and started seeing failures in our incremental models with require_partition_filter=true. Thanks @Kayrnt for the quick identification and for putting up a PR.


[RFR] Remove jQuery dependency

Hey there,
This should remove the jQuery dependency and solve #6. Be sure to test it though. :)

Hey, yes. I will open up a PR once this is ready and stable! :)

https://github.com/arbelh/HalfStyle/pull/8 Here we go.

@HugoGiraudel
Hey there,
Thanks for the contribution.
This has worked fine so far in my tests, but I will do further tests. It'd be better to add a proper DOM ready trigger to it to prevent early execution if the target elements are not loaded yet. I will release it as V3 as this is a major change and will mention you in credits!

@arbelh Glad it works! Thanks for accepting to release it! :)

@arbelh Hey, been a long time. Any timeline on when this is planned to be released?

Hey @arbelh any update on this? Is there something more that is expected from this feature?


Try bundling an emoji font

Since #403, we don't bundle a font for emoji; instead we rely on the system fonts for showing Unicode emoji. This has advantages but also disadvantages:

zulip/zulip-mobile#3885

The reason that since #403 we don't bundle a font is that we haven't found a good emoji font that works in Flutter on iOS, and although the one we were shipping seems to largely work on Android it's not clear it always does. Specifically there's this upstream issue:

https://github.com/flutter/flutter/issues/134897#issuecomment-1821594910

and the symptom when it doesn't work is that using the font produces a blank space, even when the system font would have handled the emoji just fine.
If that upstream issue gets fixed, then we should be able to just resume shipping Noto Color Emoji in its COLRv1 form.

We learned at https://github.com/flutter/flutter/issues/134897#issuecomment-1821632095 that COLRv1 fonts aren't supported on any version of iOS. I think that means Noto Color Emoji just isn't usable on iOS.
So when we go back to bundling Noto Color Emoji, we should do so on Android only. That'll need

https://github.com/flutter/flutter/issues/96514

or perhaps

https://github.com/flutter/flutter/issues/21682

; I'm not really sure what the difference is. (That latter issue has a PR that's being actively worked on.)

I'm not really sure what the difference is.

Yeah, I'm not either. I left a comment https://github.com/flutter/flutter/issues/96514#issuecomment-1828637086 on the less-trafficked issue asking for clarification on how it differs.

Even after that PR lands, it might still be somewhat annoying to have the asset just on one platform, because it looks like it doesn't directly support selecting by platform. It would make it possible to do so but only through a workaround: define a "flavor" to control including the font, and then use the no-emoji-font flavor when building releases for iOS.
An alternate solution would be to ship the font unconditionally, but only invoke it on Android; so it'd be in the iOS app bundle but wouldn't get used. I think that'd be fine through the beta period.
(This issue is currently milestoned post-launch, but given what we've discovered in trying to lay out reaction emoji just right — https://github.com/zulip/zulip-flutter/pull/410#discussion_r1402812415 — we might move it forward.)

We closed this in #436, which bundles Noto Color Emoji again and uses it in part of the app. We've split out a new issue:

#438

for using it in the rest of the app.


Update to new Fragpipe output

Hi all,
Very nice tool, I really like it!!
Fragpipe's IonQuant has recently been updated which now produces combined_peptide.tsv and combined_peptide_modified.tsv. I was wondering if this recent update can be added? The update also causes the combined_peptide.tsv not to work anymore.
Cheers,
Patrick

Ho Patrick,
thanks a lot for letting us know.
Could you send us a small example file so we can locally test it and update AlphaMap?
Thanks a lot!
Cheers,
Isabell

Hi Isabell,
Of course. See attached the combined_peptide.tsv and combined_modified_peptide.tsv files of a small dataset.
Hope it helps.
drive-download-20220223T070351Z-001.zip
Best,
Patrick


[Workers] Document that only standard ports are supported by fetch()

Product

Workers
Presumably Pages Functions

Subject Matter
When using a local development environment like Miniflare or the Workers Preview available through Quick Edit in the dashboard, using fetch() on non-standard ports is supported. As an example, fetch("https://example.org:8080") would fetch on port 8080.
However, when published into production, non-standard ports are disregarded. fetch("https://example.org:8080") would fetch on port 443 as that is the default port for the https:// scheme and fetch("http://example.org:8080") would fetch on port 80 as that is the default port for the http:// scheme.
This isn't currently documented and causes a lot of confusion when people are developing for endpoints that are on non-standard ports and since it works locally and in previews, expect it to work when published into production.
Content Location
Uncertainty around this is why I decided to make an issue rather than a PR - where do we put it?
Is it a known issue that'll be fixed, is it a known limitation that won't be changed or do we put it under the fetch or request API docs as an aside?

I’ve been told that you can fetch on non-standard ports if the request is going to the same zone - which if true, might be worth clarifying?

wrangler now logs a warning as of https://github.com/cloudflare/wrangler2/pull/992

Based on https://github.com/cloudflare/wrangler2/issues/975#issuecomment-1169126913 this is a big that will be fixed and is tracked in https://github.com/cloudflare/wrangler2/issues/1320

Superseded by https://github.com/cloudflare/cloudflare-docs/issues/5998


Legend.from_csv errno22

Hi,
I get an error when I am trying to follow the tutorial for making a legend. When I use the following code I get the [Errno 22] Invalid argument. However, I took most of the code from the tutorial, the only change I made was to remove duplicate legend items.
from striplog import Legend, Lexicon, Interval, Component, Decor, Striplog

l = u"""Colour, Component lithology
#F7E9A6, Sandstone
#FF99CC, Anhydrite
#DBD6BC, Heterolithic
#FF4C4A, Volcanic
#86F0B6, Conglomerate
"""
legend = Legend.from_csv(l)

It will try to interpret the first argument as a filename. You have to say, legend = Legend.from_csv(text=l)

That is great, thanks


Is there anyway to build offline?

I was trying to use nvbench in private network, where I can not reach github.
Is there any settings or way so that I can build this project offline?

You can always fork the project and put it somewhere reachable.
That would still require you to occasionally sync with main, but that would be a rather rare thing

@miscco the problem with cloning is that nvbench cmake files are fetching rapids cmake from github. Even if you prefetch some files before configuring cmake, I'm not sure that it'll work as expected. Rapids cmake is cloning other sub projects from github. @allisonvacanti is there a workaround for that?

I fear then the most probable solution is to clone all dependencies and adopt the cmake files to point to the internal repositories

Well in my situation, the server are completely offline, but the rapids-cmake requires to connect to github for version checking. Even if I set CPM_CACHE(sorry I forget the concrete name), the rapids-cmake still needs to connect to github.

I fear then the most probable solution is to clone all dependencies and adopt the cmake files to point to the internal repositories

I have tried to set CPM_USE_LOCAL and changed the links inside rapid_find_packages to point to local paths, but this is not working as well. If anyone is interested, I can make it public. I think the best way is to completely rewrite the cmakefiles to create another version that uses git submodule rather than rapids.

Has this been resolved?

@robertmaynard Thanks, your solution worked in my environment.


Docker container - UnknownModel

Hi,
I'm trying to run my application in a docker container. The code is the one listed in rppal main page:
use ...
const GPIO_LED: u8 = 23;

fn main() -> Result<(), Box<dyn Error>> {
    println!("Blinking an LED on a {}.", DeviceInfo::new()?.model());
    let mut pin = Gpio::new()?.get(GPIO_LED)?.into_output();
    ...
}

running on raspberry pi4 (r.os x64) works fine
running inside docker alpine with --privileged flag works fine (but a little bit too permissive)
running inside docker alpine fails (even with --device /dev/gpiomem --device /dev/mem -v /sys:/sys flags) with following errors:

UnknownModel calling DeviceInfo::new()
io(Os { code: 2, kind: NotFound, message: "No such file or directory" }) calling Gpio::new()

in all the cases I'm able to see /proc/cpuinfo. What am I missing?
/proc/cpuinfo contains
Hardware        : BCM2835
Revision          : c03112
and it should be parsed correctly to RP4B. I'll try to debug DeviceInfo::new() code.
Executing the code in master branch (parse_proc_cpuinfo function) everything works fine.
Is it possible that rppal 0.11.3 isn't aligned with master code (so it is not able to read from /proc/cpuinfo, tries to read from other locations /sys/firmware/* that without --privileged docker flag aren't availble by default)?

Ok.
If I use the source code (master), RaspberryPI 4 model B is detected correctly. The error raised by Gpio::new() is due to the fact that /dev/gpiochip0 must be shared. So, if I run:
docker run --device /dev/gpiomem --device /dev/gpiochip0 -it my-image-musl

everything works fine.


feat: use CUDA 12.4 by default (for FA3)

Motivation

Modifications

Checklist

[ ] Format your code according to the Contributor Guide.
[ ] Add unit tests as outlined in the Contributor Guide.
[ ] Update documentation as needed, including docstrings or example tutorials.

ref https://github.com/flashinfer-ai/flashinfer/pull/699


Make it possible to choose between a font's stylistic sets

Description of the new feature/enhancement
OpenType fonts often have stylistic sets that allow users to choose specific alternate characters - for example, old-style numerals instead of lining figures. However, this requires support by the software the font is used with, which is already the case with many editors and terminal emulators.
It would be great if such support were added to Windows Terminal.

@DHowett Oh, nice, thank you

/dup #1790


Support multiple init scripts in JdbcDatabaseContainer

Inspired by PRs: #2578 and #1997
Closes #2232

This feature is essential, the PR looks good, I hope it will be accepted as soon as possible, good work.

This is a must-have feature. Could anyone please approve and merge this PR?

Using private Map<String, String> initScriptPaths = new LinkedHashMap<>(); would support my use case #8634.

Thanks for your contribution, @savinov !

Looks like this change is breaking for the case when initScriptPath isn't provided. Then initScriptPaths is initialized with one null element, and then application failed when trying to get the resource in ScriptUtils.runInitScript() method.

Looks like this change is breaking for the case when initScriptPath isn't provided. Then initScriptPaths is initialized with one null element, and then application failed when trying to get the resource in ScriptUtils.runInitScript() method.

Same issue

@savinov could somebody fix it, please? Thnx in advance :)


Use flux-standard-action dependency for test only

Including FSA means adding unneeded dependencies. We keep using it inside tests so we ensure consistency. Closes #60
Note: I've removed "has no extraneous key" test because isFSA() already does that check.

Would be happy to merge this but tests are failing and we have some merge conflicts, because I've fixed the master build. Could you fix this PR?

Hi @timche, branch updated and looks like it's all green now 👍

Thanks, merged :)


Same here, lineNumberContainerStyle  does not work

          Same here, `lineNumberContainerStyle ` does not work

Originally posted by @maxpaleo in https://github.com/react-syntax-highlighter/react-syntax-highlighter/issues/347#issuecomment-2323292415

same issue :(


CSS Operating System Colors

This is more for academic purposes than anything, but I recently discovered that CSS has color keywords based on operating system definitions.
http://codepen.io/kevinSuttle/full/pbzxZZ/
I tried this in Electron, and it works, but not in RN.
Notice backgroundColor: Highlight;

Mac 10.11.5 / iOS 9.3 (SimulatorApp-645.9)
react-native-cli: 0.2.0
react-native: 0.26.2
https://facebook.github.io/react-native/docs/colors.html

The way CSS works in React Native is not exactly CSS, it is based on the css-layout library. We recently added a bunch more docs to explain how this works so hopefully those docs are clearer now. I'm going to close this issue but if you believe there is a bug or a misdocumentation somewhere feel free to reopen.


pythonPackages.jupyterhub-ldapauthenticator: init at 1.1

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@dotlambda  - whoopsy, been a little sloppy there! Fixed now, hopefully.

@GrahamcOfBorg build python3.pkgs.python3.pkgs.jupyterhub-ldapauthenticator
@ixxie You might want to add disabled = !isPy3k.

Failure on x86_64-linux (full log)
Partial log (click to expand)
error: attribute ‘python3’ in selection path ‘python3.pkgs.python3.pkgs.jupyterhub-ldapauthenticator’ not found

Failure on aarch64-linux (full log)
Partial log (click to expand)
error: attribute 'python3' in selection path 'python3.pkgs.python3.pkgs.jupyterhub-ldapauthenticator' not found

Success on x86_64-linux (full log)
Partial log (click to expand)
Installing collected packages: jupyterhub-ldapauthenticator
Successfully installed jupyterhub-ldapauthenticator-1.1
/tmp/nix-build-python3.6-jupyterhub-ldapauthenticator-1.1.drv-0/jupyterhub-ldapauthenticator-1.1
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/s708qhd4ryxiz0azlsjpab52yk43z3n2-python3.6-jupyterhub-ldapauthenticator-1.1
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/s708qhd4ryxiz0azlsjpab52yk43z3n2-python3.6-jupyterhub-ldapauthenticator-1.1/lib
patching script interpreter paths in /nix/store/s708qhd4ryxiz0azlsjpab52yk43z3n2-python3.6-jupyterhub-ldapauthenticator-1.1
checking for references to /tmp/nix-build-python3.6-jupyterhub-ldapauthenticator-1.1.drv-0 in /nix/store/s708qhd4ryxiz0azlsjpab52yk43z3n2-python3.6-jupyterhub-ldapauthenticator-1.1...
/nix/store/s708qhd4ryxiz0azlsjpab52yk43z3n2-python3.6-jupyterhub-ldapauthenticator-1.1

Success on aarch64-linux (full log)
Partial log (click to expand)
Installing collected packages: jupyterhub-ldapauthenticator
Successfully installed jupyterhub-ldapauthenticator-1.1
/build/jupyterhub-ldapauthenticator-1.1
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/a95dawf4zpxfmy9qcdlf084fsrgznpw7-python3.6-jupyterhub-ldapauthenticator-1.1
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/a95dawf4zpxfmy9qcdlf084fsrgznpw7-python3.6-jupyterhub-ldapauthenticator-1.1/lib
patching script interpreter paths in /nix/store/a95dawf4zpxfmy9qcdlf084fsrgznpw7-python3.6-jupyterhub-ldapauthenticator-1.1
checking for references to /build in /nix/store/a95dawf4zpxfmy9qcdlf084fsrgznpw7-python3.6-jupyterhub-ldapauthenticator-1.1...
/nix/store/a95dawf4zpxfmy9qcdlf084fsrgznpw7-python3.6-jupyterhub-ldapauthenticator-1.1

@dotlambda - I applied the requested changes. I didn't use the disabled = !isPy3k because the github page for the package says this could in principle work on python2 but simply wasn't tested.


Added type conversion fucntions for boolean, number, and string

Added type conversion functions and tests.

Looks good!  Please open a PR for the spec too.

Looks good! Please open a PR for the spec too.

Yep!


[Experimental] allow custom top in grammar

This is a demo to allow grammars to define a custom top.
It can cause unfinished highlighting.
Eg. top <- . will only output the first character.

I think for now the grammars should stick to the token-based parsing. If there is a compelling use-case for full language parsing, then maybe we can revisit then. One big reason to keep the token-based parsing is the automatic memoization, which is necessary for fast incremental highlighting.


Parallelization of FastRouteCore::mazeRouteMSMD

Description
A major part of global routing is spent on fixing overflows in FastRouteCore::mazeRouteMSMD. It iterates over Steiner trees representing parts of the routing, which are mostly disjoint. It should be possible to parallelize this method.
Suggested Solution
We're currently trying to parallelize the FastRouteCore::mazeRouteMSMD.
Additional Context
No response

Is this effort inspired by some of the ispd24 contest approaches or do you have something else in mind ?
https://liangrj2014.github.io/ISPD24_contest/
The largest of the ispd24 test cases OpenRoad is currently able to grt/drt in 64GB is the 715k stdcell bsg_chip.def.gz

No, I though about adjusting existing method to make it work in parallel on CPU.
I checked out the contest and it was mainly focused on GPU acceleration and ML solutions - top submissions are vaguely described in final presentation, but I found a few papers created by the top teams; I'll check whether there is something that can be used.

One of the top three didn’t use the gpu at all, so threading can help a lot with regard to runtime.
Could you point me to the papers you found ?

It would be good to describe your approach once you clarify it.  InstantGR does work with the gpu.

It seems that papers don't describe work from the contest, as they usually compare results with top three teams. But they are created by the same people, so I guess papers describe improved solutions:

1st place team - paper
2nd place team (already mentioned InstantGR) - paper, code

Both approaches use GPU.
Other papers based on ISPD24:

paper, code


Don't work @Condition with android.app.Fragment

in FormValidator.evaluateCondition():
	if (target instanceof Activity) {
		conditionView = ((Activity) target).findViewById(viewId);
	} else if (target instanceof Fragment) {
		conditionView = ((Fragment) target).getView().findViewById(viewId);
	} else if (target instanceof View) {
		conditionView = ((View) target).findViewById(viewId);
	} else {
		throw new FormsValidationException("unknown target " + target);
	}

this class imports android.support.v4.app.Fragment

fixed by 483c72c050a8c020c83094bad6de505150738d20


[BUG] Always NullReferenceException in FileStorage.Find()

Version
Using version 5.0.2
Describe the bug
Find always returns a System.NullReferenceException in any path or database we try. The same code works perfectly and was in production on Version 4.1.4.
We know there are file because Exists() and Download() is working correctly with the same paths
Code to Reproduce
    public List<string> GetFilesInPath(string path)
    {
        List<string> foundFiles = new List<string>();
        // Returns all the files in this path
        var files = db.FileStorage.Find("$" + path);
        foreach (var lf in files)
        {
            foundFiles.Add(lf.Id);
        }
        return foundFiles;
    }

Expected behavior
Should return a list with all the file ids
Screenshots/Stacktrace
Result StackTrace:
at LiteDB.BsonExpressionParser.TryParseFunction(Tokenizer tokenizer, ExpressionContext context, Boolean isRoot)
at LiteDB.BsonExpressionParser.ParseSingleExpression(Tokenizer tokenizer, ExpressionContext context, Boolean isRoot)
at LiteDB.BsonExpressionParser.ParseFullExpression(Tokenizer tokenizer, ExpressionContext context, Boolean isRoot)
at LiteDB.BsonExpression.Parse(Tokenizer tokenizer, BsonExpressionParserMode mode, Boolean isRoot)
at LiteDB.BsonExpression.Create(String expression)
at LiteDB.BsonExpression.Create(String expression, BsonValue[] args)
at LiteDB.LiteStorage`1.Find(String predicate, BsonValue[] args)
at ....
Result Message:
Method threw exception:
System.NullReferenceException: Object reference not set to an instance of an object.

FileStorage.FindAll() is also affected...

Hi @duduric,
FileStorage works a bit different in v5. There is no more restriction about _id type in _files collection. In v4, _id is the filename with path. In v5, is any unique _id (with any data type you what, like string, int, ...). So, the Find() method change to implement any type of query over _files. You can write like:
fs.Find("_id LIKE @0", path + "%")
or
fs.Find("_id = @0", path);
or
fs.Find("filename = @0", filename)

@deje07, yes, it's a bug. I'm fixing this. For now you can use some like fs.Find("1 =1")

Thanks, we have been able to fix this part of the code

Hi @mbdavid , could you change FileStorage section on https://www.litedb.org/docs/filestorage/ ?
Example described doesnt work anymore
// Find all files references in a "directory"
var files = fs.Find("$/photos/2014/");


New Directory

Is your feature request related to a problem? Please describe.
Not a big problem : When you want create a new directory, the focus is not in the zone where you type the name of the new directory. I must click in the zone and after i can name the directory.
Describe the solution you'd like
Please, get the focus in this zone, then i will save a click ;)
Describe alternatives you've considered
Just click in the zone before typing
Additional context
I talk about this zone : version <IP_ADDRESS>

Thanks for this report. This issue has been fixed on the development version.


Error when trying to add new Subscriber

Hello, I am trying to add a new subscriber using go and gin-gonic, but I keep getting an error
"error": "POST https://connect.mailerlite.com/api/subscribers: 422 The groups field must be an array. map[groups:[The groups field must be an array.]]",
Here is my code
var MAILERLITE_API = os.Getenv("MAILERLITE_API")
func SaveNewsletter() gin.HandlerFunc {
	return func(c *gin.Context) {
		client := mailerlite.NewClient(MAILERLITE_API)
		ctx := context.TODO()
		subscriber := &mailerlite.Subscriber{
			Email<EMAIL_ADDRESS>			Fields: map[string]interface{}{
				"city": "Vilnius",
			},
		}
		newSubscriber, _, err := client.Subscriber.Create(ctx, subscriber)
		if err != nil {
			c.JSON(http.StatusInternalServerError, gin.H{"success": false, "error": err.Error()})
			return
		}
		log.Println(err, newSubscriber)
		c.JSON(http.StatusOK, gin.H{
			"success":    true,
			"subscriber": newSubscriber.Data,
		})

	}
}

If you don't need to add groups you can probably make it work by adding:
Groups: []mailerlite.Group{},
like this:
subscriber := &mailerlite.Subscriber{
			Email<EMAIL_ADDRESS>			Fields: map[string]interface{}{
				"city": "Vilnius",
			},
			Groups: []mailerlite.Group{},
		}

If you need to add groups like Im trying to do now, this won't work because the api is expecting a list of strings instead of a list of mailerlite.Group{}. Probably a new struct should be created for the creation of subscribers

open to PR's to fix this 👍

you can now submit this without groups, im trying to think of the best way to handle subscriber groups 🤔 i would hate to have to introduce a new type just for this NewSubscriber for example


Stay reasonably neutral in problem statement

Given the long history of controversy around the topic, I think the problem statement reads somewhat tendentious and thus can be misunderstood as unalterable facts, which in part is not the case.
In particular, the Component Model's choice to only support USVString is called a requirement herein, even though the Component Model is merely in phase 1, is about to be formally objected to with the next phase advancement, and could trivially support DOMString as well (adhering to precedents like WebIDL, JSON, the many language standards etc.) so Java-like languages are not unnecessarily confronted with friction when interfacing with JS, themselves or each other. Some people, including myself, consider the Component Model's choice as arbitrary for this reason, as it really inserts conceptional discontinuity in between two things that would otherwise work just fine if DOMString was supported, which would significantly reduce the scope this proposal has to cover.
I hence propose to remain neutral in the problem statement, so prior discussion is taken into account and people don't have a reason to feel too strongly over the reasoning.

Thinking a bit more about how to deal with differing strong opinions in a neutral way, I think there are two valid options:

Balance: Briefly summarize both opinions if the context is considered noteworthy.
Abstention: Do not mention either opinion and phrase very carefully so nothing is implied.

I've tried to adhere to these in my latest edit and am looking forward to your suggestions if you think there are further improvements.

@dcodeIO I think you're overthinking things. The purpose of this explainer is to make a compelling argument for the utility of the proposed features. The level of nuance you're looking to include here doesn't seem like it would help with that, and may, in its verbosity, actually take away from it. I'm willing to make the changes we discussed above if you would still prefer that to the current text. Otherwise I'm inclined to stop trying to resolve this concern and either leave the README as-is or remove all mentions of wasm/wasi. I'm confident that this proposal is sufficiently motivated even in their absence.

Please allow me a little more time to figure out if I can come up with a different structure respectively a shortened account, as I am so far not seeing any suggestions or discussions that would contribute to the title respectively intent of the PR. An alternative approach might be that additional context is moved to the FAQ, so related questions are reasonably answered. Would this be something you'd be comfortable with?

@dcodeIO Sure, let me know when you'd like another review, but please keep in mind the purpose of the explainer.

I would not agree that I'd somehow not keep the purpose of the explainer in mind. That's not what my prior acknowledgement acknowledges, and I am convinced that I have so far provided a reasonable line of arguments in support of my contribution.


DiagnosticSource errors building latest Npgsql provider

Since I started syncing with preview3/rtm, trying to build the Npgsql functional tests project with netcoreapp2.0 fails:
Microsoft (R) Build Engine version 15.3.388.41745 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  EFCore.PG -> C:\projects\Npgsql.EntityFrameworkCore.PostgreSQL\src\EFCore.PG\bin\Debug\netstandard2.0\Npgsql.EntityFrameworkCore.PostgreSQL.dll
  EFCore.PG.FunctionalTests -> C:\projects\Npgsql.EntityFrameworkCore.PostgreSQL\test\EFCore.PG.FunctionalTests\bin\Debug\net461\Npgsql.EntityFrameworkCore.PostgreSQL.Funct
ionalTests.dll
C:\Program Files\dotnet\sdk\2.0.0-preview2-006497\Microsoft.Common.CurrentVersion.targets(1984,5): warning MSB3277: Found conflicts between different versions of the same d
ependent assembly that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed. [C:\projects\Npgsql.EntityFramew
orkCore.PostgreSQL\test\EFCore.PG.FunctionalTests\EFCore.PG.FunctionalTests.csproj]
Utilities\NpgsqlDatabaseCleaner.cs(16,21): error CS1705: Assembly 'Microsoft.EntityFrameworkCore' with identity 'Microsoft.EntityFrameworkCore, Version=<IP_ADDRESS>, Culture=neu
tral, PublicKeyToken=adb9793829ddae60' uses 'System.Diagnostics.DiagnosticSource, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' which has a higher vers
ion than referenced assembly 'System.Diagnostics.DiagnosticSource' with identity 'System.Diagnostics.DiagnosticSource, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b
13ffcd2ddd51' [C:\projects\Npgsql.EntityFrameworkCore.PostgreSQL\test\EFCore.PG.FunctionalTests\EFCore.PG.FunctionalTests.csproj]

Note that the EF Core provider itself builds just fine, and the test project also builds fine with net461. Oddly enough I have no issues compiling EF Core itself (i.e. the SqlServer provider). As we're starting to near RTM I thought I'd ask right away.
This is the csproj in question.

See https://github.com/aspnet/EntityFramework/commit/8f120e03d70aa6e0cedb790671d883bdc14ca7f7
For some reason DiagnosticSource was moved from 4.4.0-* to 4.4.1-* which has different assembly version. You would run into such conflict if your dependencies are referring to different versions and no assembly redirect. I believe explicitly adding reference to it would resolve it.

Hmm, adding <PackageReference Include="System.Diagnostics.DiagnosticSource" Version="4.4.1-*" /> to both the provider project (EFCore.PG) and the functional test project hasn't made the error go away.

@roji - Do you get error when building or running tests? I cannot run functional tests because no npgsql installed.
Though I found 1 weird thing while building.
https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/blob/dev/build.ps1#L36
Why you are using release version of KoreBuild? That is really old one. & the branching strategy for KoreBuild been really bad. If you are trying to sync up with nightly builds then I recommend using dev.zip (that's how I got the project to build correctly.)

Ok found the error. Related issue #9124
Change your KoreBuild to dev which will download latest CLI. And use the latest CLI for testing. (preview2 rtm CLI won't work).
The reason we had to upgrade the version is underlying CLI started using newer one.
I managed tests to start while using latest CLI.

@smitpatel when building - no need to run the tests. Are you saying you've managed to build the functional tests project with no errors on netcoreapp2.0?
build.ps1 and friends are really old and unused, I've only been building the sln/csproj directly for a long while now.  I'll remove it.

Messages crossed :)
OK, I'll try the latest CLI and report back, thanks!

FYI on https://github.com/dotnet/cli is talking about 2.1.0-preview1-006723, either you guys are really fast with the next version or there's some version mismatch??

sln/csproj directly would work as long as you are depending on last release of EFCore.
15.3 preview 3 + .NET SDK preview2 + EFCore packages preview2-final will work without any error.
If you take nightly builds then EFCore depends on newer CLI so you need to install latest nightly SDK too.
The current SDK EF is depending on is here https://github.com/dotnet/cli/tree/release/2.0.0#installers-and-binaries
build.* script downloads and install latest CLI via KoreBuild. Its not necessary step but then you have to install required CLI yourself.

 Check release/2.0.0 branch. That's what we are depending on at present. Once we branch, branches will be in sync. We are bit slow than dotnet 😞

Confirmed, using dotnet cli 2.0.0-preview3-006694 to build works fine without any errors, thanks!

cc @ErikEJ , @Kagamine - If you guys hit this issue

Thanks, salve is .net 4.6.1 only, so I assume this does not apply?

@ErikEJ I was just fine with .net 4.6.1, you probably don't need to do anything.

@caleblloyd


Content Observers can't detect the fuel slot of furnaces/blast furnaces/smokers

Describe the Bug
Content Observers can't detect the fuel slot of furnaces/blast furnaces/smokers.
In Forge version of create, they can.
Reproduction Steps

Put a furnace/blast furnace/smoker.
Put a carpet in the fuel slot.
Put a content observer and let it detect the furnace.
It can't detect the carpet.

Expected Result
It should detect the carpet properly like the forge version.
Screenshots and Videos

Crash Report or Log
No response
Operating System
macOS 12.2 Beta (21D5039d)
Mod Version
0.4.0c
Minecraft Version
1.18.1
Other Mods
[✔] architectury-3.4.9
[✔] c2me-fabric-mc1.18.1-0.2.0+alpha.6.1-all
[✔] cloth-api-3.0.55
[✔] cloth-config-6.1.48-fabric
[✔] create-mc1.18.1_v0.4c
[✔] EntityCulling-Fabric-1.3.3
[✔] fabric-api-0.46.1+1.18
[✔] Flywheel-Fabric-1.18-<IP_ADDRESS>
[✔] indium-1.0.2-alpha2+mc1.18.1
[✔] krypton-0.1.6
[✔] lazydfu-0.1.2
[✔] lithium-fabric-mc1.18.1-0.7.7
[✔] mcwifipnp-1.5.3-1.18-fabric
[✔] modmenu-3.0.1
[✔] notenoughcrashes-4.1.4+1.18.1-fabric
[✔] rer-2.3.0
[✔] RoughlyEnoughItems-7.1.380
[✔] slight-gui-modifications-2.0.2
[✔] smoothboot-fabric-1.18-1.7.0
[✔] sodium-extra-mc1.18.1-0.3.8
[✔] sodium-fabric-mc1.18.1-0.4.0-alpha6+build.14
[✔] starlight-1.0.1+fabric.0583973
[✔] wthit-fabric-4.4.1
Additional Context
No response

This is due to a limitation with FAPI transfer. Fabric simply doesn't have a concept of "not-sided."
I've mitigated this with this commit, however now you won't be able to detect the input slot or the output slot. It'll behave more as expected, but not exactly the same as forge.

There is no way for us to fix this - either FAPI changes (not happening) or upstream changes (plausible). I've already brought it up to the forge team. If neither change, this has been promoted to Feature™.

Nevermind! I managed to throw something together that emulates forge's no sides by getting all sides and merging them. It seems pretty unstable though, testing appreciated. fixed in this commit.

Will test it! Thanks a lot!


register with system account and trigger no matter user is

Hi sirs,
may i register with system account and trigger event no matter user is?
currently trigger events only login user match with registrations user.
thanks.

Yes, you can send events to any subset of your users using the model described here:
https://blogs.msdn.microsoft.com/webdev/2015/12/31/new-year-updates-to-asp-net-webhooks-preview/
Hope this helps!
Henrik

Use NotifyAllAsync Method.
I got it. thank for your help.


On iOS, changing the value of multiline when a TextInput is focused forces the keyboard to be dismissed.

Description
If you have a dynamic value for multiline on a TextInput, changing its value will cause the keyboard to get dismissed.
This makes it difficult to make a messenger-like input that is a single line when out of focus and multiline when focused.
Note that this does not happen on Android. It also does not happen if there is no way to manually blur the input (for example a scroll view that can be tapped on)
React Native version:
  Binaries:
    Node: 10.15.3
    Yarn: 1.22.0
    npm: 6.14.5
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz => 0.62.2

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Create a component with a TextInput and a ScrollView (the text input does not need to be inside the view)
Make the multiline value of the TextInput change when it gets focused
You should notice that you have to tap the TextInput multiple times to keep the keyboard up

Expected Results
The keyboard should stay visible without having to tap the input again. The way it does on Android.
Snack, code example, screenshot, or link to a repository:
https://snack.expo.io/@divone/changing-multiline-removes-focus

Maybe duplicated #29569?
And I had made a PR https://github.com/facebook/react-native/pull/29580.
Please check whether this pr is work for you 😄.

Hello!
Unfortunately, I am using expo and I cannot change this part of the code :(

Hello!
Unfortunately, I am using expo and I cannot change this part of the code :(

OK! I will try to test it.

Unfortunately, It seems to be a different issue.
I will try to figure it out later, sorry.


main.go:14: make KeyFile configurable.

The puzzle 5-8fb4a9a8 from #5 has to be resolved:
https://github.com/kerelape/gophkeeper/blob/8f3176921e60b1af7bcb0b0e826f328e31b738aa/cmd/server/main.go#L14-L14
The puzzle was created by kerelape on 28-Aug-23.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 5-8fb4a9a8 has disappeared from the source code, that's why I closed this issue.


chore: Consolidate subnet & AZ configs in VPC config

Description of changes

Refactor VPC config shapes to consolidate subnet and availability zone configurations, including moving the proxy, cluster, and instance discovery logic into separate files to make vpc-helper a bit easier to read
Update starting Lambda Layer version

Description of how you validated changes
Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Looks like you need to run yarn extract-api still.

Looks like you need to run yarn extract-api still.

Thanks, done!

rds-import-vpc.test.ts e2e test passes locally

Rebased against latest feature branch changes


RuntimeError: CUDA out of memory.

During running Omegafold in ubuntu 22.04 (RAM= 16 G, Cpu= i7-6700K, GPU= GTX 750 Ti), I got the following error for a peptide with 8 residues.

Hi,
Unfortunately it might be not possible to run the model on a 2GB-ram card. You could try to set --subbatch_size to 1 and see if it runs. If it does not run and output the same error stack, then we suggest you get access to a larger card (through colab, for example).
Best


cmd/internal/obj: add prologue_end DWARF stmt for ppc64

This patch adds a prologue_end statement to the DWARF information for
the ppc64 arch.
Prologue end is used by the Delve debugger in order to determine where
to set a breakpoint to avoid the stacksplit prologue.
Updates #36612

cc @dr2chase @aarzilli @heschik


html/template does not support javascript module

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

$ go version
go version go1.12 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/daniel/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/daniel/.go"
GOPROXY=""
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build067538039=/tmp/go-build -gno-record-gcc-switches"

What did you do?
The following code creates an html/template Template, and passes in a struct inside a script tag with type "module" (for reference: https://developers.google.com/web/fundamentals/primers/modules)
package main

import (
	"bytes"
	"fmt"
	"html/template"
)

type mystruct struct {
	Foo string `json:"foo"`
	Bar int    `json:"bar"`
}

func main() {
	b := new(bytes.Buffer)
	tpl := template.Must(template.New("moduletest").Parse(`
	<html>
		<body>
		<script type="module">
			var properties = {{ . }};
		</script>
		</body>
	</html>
	`))
	tpl.Execute(b, mystruct{
		Foo: "Hello World",
		Bar: 42,
	})

	fmt.Printf("%s", b.String())

}

What did you expect to see?
This is the result when I remove type="module", and is what I expected to see:
<html>
	<body>
	<script >
		var properties = {"foo":"Hello World","bar":42};
	</script>
	</body>
</html>

What did you see instead?
<html>
	<body>
	<script type="module">
		var properties = {Hello World 42};
	</script>
	</body>
</html>

I considered a pull request adding module to the recognized mime-types for html template, but since modules use import syntax/have other features that might not be handled by the current template code, I decided to hold off.

We already https://go-review.googlesource.com/c/go/+/135417 for this.

oops, my bad - I didn't notice the extra issue tracker.


Floating panel event listeners

Is your feature request related to a problem? Please describe.
I'm trying to implement a UI using floating panels. One requirement is for the panels' positions to persist when the page is refreshed. Currently this is not possible because there are no event listeners available for when a floating panel is moved or closed.
Describe the solution you'd like
Expose event listeners for when a floating panel is moved or closed.
Describe alternatives you've considered
Currently I'm using the SerializedDockview to get panel position, and I've hidden the close button by using a custom tab component. I'm using external controls to add/remove panels, and before that occurs I store the panel's position in local storage. This works fine when hiding/showing the panels with my external controls, but moving a panel and then refreshing the page results in losing the latest position data.

As long as that includes the top, right, bottom. left data that would be great! Would that also fire when a panel/group is closed?

In regards to the panel/group closing is there a reason why you couldn't use api.onDidRemoveGroup / api.onDidRemovePanel?
Also of of interest what is the reason you require the top, right, bottom, left data? Are you persisting your layout without using the built-in api.toJSON() and api.fromJSON() methods?

In regards to the panel/group closing is there a reason why you couldn't use api.onDidRemoveGroup / api.onDidRemovePanel?
This does appear to do what I need, however the position value in the fromJSON method is strange. For some reason, bottom and right are required according to Typescript, but they're not always provided in the JSON returned from that method. I'm probably misunderstanding something though.

Also of of interest what is the reason you require the top, right, bottom, left data? Are you persisting your layout without using the built-in api.toJSON() and api.fromJSON() methods?
Because once a panel is closed, it's gone. I need a reference to closed panels, so when I need to open it again, it can appear in the same spot it was in when it was closed. It would actually be a lot easier if you could define panels and then just toggle their visibility rather than removing/adding them completely.


Populate help page

Populate the help page with content from the GoogleDocs description.
Only change to the text is to specify that stories are stored in OpenHumans
Contributes to issue #460 but does not complete it

Requesting feedback from @GeorgiaHCA about linking to the code of conduct page. There are two options in the screenshot above (and in the html) which is preferred - inline or button? (or is there a third option?)

@helendduncan: are you still waiting on an answer concerning the way to present the link? I'd approve this as soon as it's resolved.

This is looking great - thanks @helendduncan !  My instinct at this point is that a button link would be better than an inline link - it just seems more clear and separated. Happy for you to go ahead and merge!


Error:  java.lang.NullPointerException: Cannot invoke "java.util.Map.entrySet()" because "entries" is null

We are using dependency check action in our github pipeline:
    - name: Run Dependency Check
      uses: dependency-check/Dependency-Check_Action@main
      id: Depcheck
      with:
        project: 'test'
        path: '.'
        format: 'HTML'

    - name: Archive Dependency Check Report
      uses: actions/upload-artifact@master
      with:
        name: Depcheck report
        path: ${{github.workspace}}/reports

We are getting the error:
Error:  java.lang.NullPointerException: Cannot invoke "java.util.Map.entrySet()" because "entries" is null
Full log:
  with:
    project: test
    path: .
    format: HTML
    out: reports
  env:
    SOLUTION_FILE: ./Space.Service.Common.Factory.sln
    PACKAGE_NAME: Space.Service.Common.Factory
    SPACE_NUGET_URL: https://nuget.pkg.github.com/SpaceBank/
    DOTNET_ROOT: /home/runner/.dotnet
/usr/bin/docker run --name c044[2](https://github.com/SpaceBank/Space.Service.Common.Factory/actions/runs/4497516738/jobs/7913183548#step:12:2)d490c5c076[3](https://github.com/SpaceBank/Space.Service.Common.Factory/actions/runs/4497516738/jobs/7913183548#step:12:3)7[4](https://github.com/SpaceBank/Space.Service.Common.Factory/actions/runs/4497516738/jobs/7913183548#step:12:4)[5](https://github.com/SpaceBank/Space.Service.Common.Factory/actions/runs/4497516738/jobs/7913183548#step:12:5)72ae5c0f5d114f2c8f_ad1710 --label [6](https://github.com/SpaceBank/Space.Service.Common.Factory/actions/runs/4497516738/jobs/7913183548#step:12:6)c0442 --workdir /github/workspace --rm -e "SOLUTION_FILE" -e "PACKAGE_NAME" -e "SPACE_NUGET_URL" -e "DOTNET_ROOT" -e "INPUT_PROJECT" -e "INPUT_PATH" -e "INPUT_FORMAT" -e "INPUT_OUT" -e "INPUT_ARGS" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/Space.Service.Common.Factory/Space.Service.Common.Factory":"/github/workspace" 6c0442:d490c5c0[7](https://github.com/SpaceBank/Space.Service.Common.Factory/actions/runs/4497516738/jobs/7913183548#step:12:7)6374572ae5c0f5d114f2c[8](https://github.com/SpaceBank/Space.Service.Common.Factory/actions/runs/4497516738/jobs/7913183548#step:12:8)f  "--project" "test" "--scan" "." "--format" "HTML" "--out" "/github/workspace/reports" "--noupdate" ""
[INFO]

Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user’s risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.

   About ODC: https://jeremylong.github.io/DependencyCheck/general/internals.html
   False Positives: https://jeremylong.github.io/DependencyCheck/general/suppression.html

💖 Sponsor: https://github.com/sponsors/jeremylong

[INFO] Analysis Started
[INFO] Finished Archive Analyzer (0 seconds)
[INFO] Finished File Name Analyzer (0 seconds)
[INFO] Finished Nuspec Analyzer (0 seconds)
[WARN] An error occurred while analyzing '/github/workspace/Space.Service.Common.Factory.UnitTests/Space.Service.Common.Factory.UnitTests.csproj' (MSBuild Project Analyzer).
[WARN] An error occurred while analyzing '/github/workspace/Space.Service.Common.Factory/Space.Service.Common.Factory.csproj' (MSBuild Project Analyzer).
[INFO] Finished MSBuild Project Analyzer (0 seconds)
[INFO] Finished Assembly Analyzer (12 seconds)
[INFO] Finished Dependency Merging Analyzer (0 seconds)
[INFO] Finished Version Filter Analyzer (0 seconds)
[INFO] Finished Hint Analyzer (0 seconds)
[INFO] Created CPE Index (2 seconds)
[INFO] Finished CPE Analyzer (4 seconds)
[INFO] Finished False Positive Analyzer (0 seconds)
[INFO] Finished NVD CVE Analyzer (0 seconds)
[INFO] Finished Sonatype OSS Index Analyzer (1 seconds)
[INFO] Finished Vulnerability Suppression Analyzer (0 seconds)
[INFO] Finished Known Exploited Vulnerability Analyzer (0 seconds)
[INFO] Finished Dependency Bundling Analyzer (0 seconds)
[INFO] Finished Unused Suppression Rule Analyzer (0 seconds)
[INFO] Analysis Complete (1[9](https://github.com/SpaceBank/Space.Service.Common.Factory/actions/runs/4497516738/jobs/7913183548#step:12:9) seconds)
[INFO] Writing report to: /github/workspace/reports/dependency-check-report.html
Error:  java.lang.NullPointerException: Cannot invoke "java.util.Map.entrySet()" because "entries" is null
Error:  java.lang.NullPointerException: Cannot invoke "java.util.Map.entrySet()" because "entries" is null

adding Directory.Build.props file to the root folder of the solution (where .sln is located), solves the issue for now:
<Project>
 <PropertyGroup>
 </PropertyGroup>
</Project>

Same behavior as in my pipeline.
Appear from version 8.2 (yesterday run with  version 8.1.2 was OK)

We are also experiencing the same issue.
At first we are getting the same warning for all MSBuild Projects and afterwards same amount of errors with :
Error:  java.lang.NullPointerException: Cannot invoke "java.util.Map.entrySet()" because "entries" is null

duplicate of #5579.


Add Xnview

Merged to: https://github.com/juno-fx/Terra-Official-Plugins/tree/pack-additional-software
Closing.


StateCheckpointers added for efficient state serialization

This PR adds proper StateCheckpointers (and tests for these) for the OperatorStates held by the KVStore operators:

The HashMap of Key-Value pairs
The Treemap of pending operations for TimeStamped KV stores
The partially merged values for multiget operations

These operators now also use the proper Flink serializers allowing for key-value types that don't implement the Java Serializable interface.
The PR is pending on an already pushed fix to Flink that resolves an issue with the serialization of default state values for partitioned operator states.

The fix commit in Flink is now in the snapshot build.

Pretty cool stuff ^^
I would merge it as it is (perhaps after adding minor docs), there are no obvious errors and the tests seem to pass. Nicely done :+1:


Does something like luasnip-expand exist?

I currently have two types of keybinds for LuaSnip. One keybind expands or jumps, this is <cr> for me, and I have one type of keybind that only jumps, like <tab> and shift + <tab>. What I actually want is for <cr> to only allow expansion of snippets, not jump in snippets.
What sometimes happens is that I'm inside a snippet and want to add a new line. But in order to do that I first have to remove all snippet jump locations. One way to resolve this would be to expand snippets with <tab> instead of <cr> but I really don't want to move snippet expansion to <tab>, because I view snippet expansion as a type of completion and I like having all completions on <cr>. So I don't like that way of resolving this.
Is there currently a way to bind <cr> to only expand and not jump? If yes, is there also some kind of function like  luasnip#expandable()? I tried looking through the source code and I don't think I found anything that looks like what I want.

Both are missing but are pretty easy to implement.

Hah, yeah they're pretty useful and easy, I'll add them :sweat_smile:

Okay, I added them as luasnip#expandable and <Plug>luasnip-expand-snippet (would've used <Plug>luasnip-expand, but I ignored proper style for those bindings and now that would collide with <Plug>luasnip-expand-or-jump, if there are more, similarly named bindings I'll do some breaking changes.)


What is the desired behavior of helm regarding manual changes?

While dealing with https://github.com/kubernetes/helm/issues/1844 the question from the subject came up.
Our position in this is best described in the https://github.com/kubernetes/helm/issues/1844#issuecomment-274112471 by @wjkohnen:

We still can reproduce stale environment variables as mentioned in 1. of https://github.com/kubernetes/helm/issues/1844#issuecomment-274112471. When we manually add, change, delete (kubectl edit deployment) environment variables, we had expected a chart upgrade to revert any of these changes so as to reflect the state that is expressed in the chart. Any deviance from the expressed state of a chart in our view degrades the idempotency of helm releases and thus the idea of k8s clusters to be "self-healing". After spending some time tackling these issues I have some intuition that this desired behavior is (currently) not feasible. We'd appreciate some clarification.

Our ideal case is that Helm upgrades would essentially work like Kubernetes apply, but at the release level instead of at the individual resource level. We are gradually getting closer to that (moving) target.
During an upgrade, the chart is rendered into resource definitions. Then a patch set is calculated by comparing those resources to the existing release's resources. Then the patch set is sent to the Kubernetes API server. As with Git, Helm will try to merge the new changes without touching unrelated changes you made with kubectl (in that sense, it "ignores" the changes in-cluster and lets Kubernetes sort it out).
So, for example, if you deploy with replica count 4, then use kubectl to raise the replica count to 6, then use Helm to upgrade the release, the replica count should remain 6.
As a consequence of this, it is not safe to assume that you can use kubectl to make arbitrary changes to a release, and then rely upon Helm to revert those changes. To accomplish that, I believe you'd have to use Helm to delete/rollback. Or, better yet, only use Helm to make changes to your release. Then you will have not only a record of what you changed, but the helm history and helm rollback commands to get you out of a bind.
/cc @adamreese

What happens if a bad release goes out? I've encountered a situation where a value was typo'd, and Kubernetes rejected the patch set.. but somehow helm thought the change went through, and adjusting it didn't fix the deployment.

@cblecker I have seen something like that as well and I could not reproduce it with helm v2.2.x. See my last comment in #1844.

@technosophos: RE https://github.com/kubernetes/helm/issues/2070#issuecomment-284839395 -- is there a way to debug output the patch set to have more insight into what's actually being applied? It's a bit scary for the chart's debug output to desync with what's actually happening in the cluster. A kubectl apply of the whole object was assumed on my part.

I believe @adamreese is working on that. There's also the helm-diff plugin.

We're hitting this with these versions:
workstation $ helm version
Client: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b8dab6c2d45be6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b8dab6c2d45be6", GitTreeState:"clean"}

We've made kubectl edit fixes  in our production environment  for:

changing Deployment replicas
changing Deployment container image tags
changing  container resources/limits

Number 1  & 2 were not reverted by the  next deploy. This is especially concerning with container image tags. Essentially what that boils down to is that if someone makes a change with kubectl edit, then we cannot be sure that hem upgrade puts things as  they are in chart.

@technosophos I think I understand the logic that Helm is keeping an history of the changes and does not override changes done manually with kubectl but that in fact prevents the use of Helm to establish a known state based on values passed to Helm charts.
Any plan for an option to force helm to apply an upgrade of resources with the values passed ?

Any plan for an option to force helm to apply an upgrade of resources with the values passed ?

You mean like helm upgrade --force?

@bacongobbler --force did not apply the values as I expected it would

I hope helm would not revert changes to the replica count as this would break horizontal autoscalers


[Fix][#39] SessionInfo.expirationTime access on android crashing

https://github.com/SAP/gigya-flutter-plugin/issues/39
Fix for the above reported issue.
Crash on android:
Uncaught Error: TypeError: "0": type ‘String' is not a subtype of type 'double'
expireIn value is received as string and incase of android it doesn't parse to double.
  Future<void> setSession(
      String sessionToken, String sessionSecret, double expiration)

Accessing above method with Session instance values throws the exception in android works fine in iOS.

@jabershabeek In my refactor PR #41 I made the expiration an int (instead of a double), which makes this PR redundant.

Fixed with the release of v1.0.0


Avoid merged in code picking up directives from main module

Fixes https://github.com/cython/cython/issues/1071
Related to https://github.com/cython/cython/commit/4c02adc906a55cd5ac663b2bb62418cf1132092f

Thanks!


Jpg page load finishes late

When loading the JPG, the image appears instantly in the browser but the network connection remains open for about 2 seconds.

I am not doing anything special with the network connection as you can see from the code. Not sure what you are asking me to do about this?

I was not paying much attention to the JPG aspect of it - the focus was on the video feed obviously.
Would adding client.stop() after
https://github.com/arkhipenko/esp32-mjpeg-multiclient-espcam-drivers/blob/master/esp32-cam/esp32-cam.ino#L368
help?

The issue is that the image is already displayed in the browser but it takes another two seconds until it stops loading. It seems the browser is expecting something, i.e. a \r\n.
I already tried Client.stop but that didn't help. The streaming (also jpg) is done asynchronously, that may be why.
The long loading times cause issues with my home automation. It times out.


Update development.md

fixed links on Dev landing page

Docs Build status updates of commit e073b7f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/development.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


locked tab

Before you start...

[X] Have you refreshed the page? You might be using an old version of the website.
[X] Have you checked if someone already requested this feature? If they have, post a comment with your use case instead.

Description
hope some of the tabs can be locked, ie. when a tab is locked, double click the folders within the tab will open a new tab, instead of go into the folder in the same tab.
for example, assume I have the below folders :
D:\folder_a
D:\folder_a\folder_b
if I have a folder_a tab, and the tab is locked, within the tab if I double click folder_b, a new tab with folder_b is created instead of changing the tab from folder_a to folder_b.
This  feature is very useful for creating shortcuts of frequently used folders, would save a lot of time if these folders are within many levels of folder structure.
Thanks.
Alternative solutions
No response
Relevant Assets
No response

@Shengwuei this repo is for the website, I think you're looking for https://github.com/files-community/Files.


Example of a chaincode using role-based access control (RBAC)

The PR contains a chaincode showing how to implement role-based access control using TCerts.
This addresses Issue #1207.
Signed-off-by: Angelo De Caro<EMAIL_ADDRESS>

Why does rbac.yaml contain a complete copy of core.yaml? My concern is that we will not be able to keep these in sync.
Also, is it possible to include a README with this chaincode describing its functionality? I'd preferably like to do that for all example chaincodes.

Hi @srderson, this chaincode is part of a joint effort with @jeffgarratt to write behave tests for the access control mechanism supported by the fabric.
A copy of core.yaml is there for test purposes. It will not stay there forever. In fact, once the client sdk will be ready I will write an app to show how to invoke the chaincode leveraging the client sdk drectly. Actually, having a test that shows how to invoke such a chaincode will help us driving the design of the client sdk to ensure that all the required API are exposed as expected. What do you think?
For the README, I will write it soon :)

@adecaro @jeffgarratt So it looks like this chaincode is deployed in the rbac_test.go test case? Is it possible to use a behave test instead? The unit tests where chaincodes are deployed are generally fragile. Ideally I think they should all be moved over to behave tests.

@srderson, Indeed, rbac_test simulates a minimal fabric environment, deploys the chaincode and invokes it in order to test its behavior. Actually, the final goal is to have behave tests. I'm just concerned that without the client sdk, it would be difficult to run successfully any behave test because the CLI (nor the REST API) does not provide the required API to drive the chaincode.
Anyway, I will try to understand if we can have something cleaner without waiting the client sdk before merging :)

@adecaro @srderson The behave test could be implemented as part of the effort I am working on now.  Either #1139 or #961.

@srderson  should we wait for the behave tests to merge or just merge it since it is a example chaincode?

@binhn I'd like to avoid merging rbac.yaml and rbac_test.go. The current effort is to remove these types of tests, not add more. Also, I'd really like to see a README with all example chaincodes, at least documenting their purpose and API.

@binhn @srderson  I also think we can wait the behave tests to merge. I'm working with @jeffgarratt to have them ready asap.

@adecaro could you please fix the license in these new files? It should be the text that I have in PR #1288 thanks

@adecaro @srderson I need to touch base with @adecaro and work this workflow.  Have come to a block point based upon current flow (which is already a bit precarious).

Hi @christo4ferris, I have updated the license and also added a readme file to describe the chaincode.
@christo4ferris, @jeffgarratt, @srderson I can also add a demo app like I did for the asset management chaincode to show how to invoke it. What do you think?

@adecaro @srderson @binhn Want to hold this PR until it is reconciled with TCert with attrs example.

Can this be closed and then reopened when its ready?

this needs some unit/function tests


Don't understand if embedder is working or not

I was trying this simple example:
import { AdaEmbeddings, Anthropic, CohereEmbeddings, HuggingFace, PdfLoader, RAGApplicationBuilder, SitemapLoader, WebLoader, YoutubeLoader } from '@llm-tools/embedjs';
import { HNSWDb } from '@llm-tools/embedjs/vectorDb/hnswlib';

import 'dotenv/config';
console.log(`Database name is ${process.env.OPENAI_API_KEY}`);
const llmApplication = await new RAGApplicationBuilder()
// .setModel('NO_MODEL')
.setModel(new HuggingFace({ modelName: 'mistralai/Mixtral-8x7B-Instruct-v0.1' }))
.setEmbeddingModel(new CohereEmbeddings())
.setVectorDb(new HNSWDb())
.build();

await llmApplication.addLoader(new PdfLoader({ filePathOrUrl: 'https://bohacales.wordpress.com/wp-content/uploads/2013/06/the-encyclopaedia-metallica.pdf' }));

var context = await llmApplication.getContext("What's Metallica's second album?");

for (var cnt of context) {
    console.log(cnt.pageContent);
}

console.log((await llmApplication.query("What's Metallica's second album?")).result);

The LLM response is correct, but I think that that response is derived by previous LLM model instruction and not from embedding.
I think so because I print all context data retrieved by cohere embedding and there is no information about the name of the album.
What am I doing wrong? Is it a bug or it's me?

You can use the debug logs (setting DEBUG=embedjs:* to the environment) to see what is the context picked up, filtered, etc. You can also verify this from the sources array in the query response.
Sorry about the delayed response. The library has been extensively refactored and docs updated. Could you reopen the issue if it is an issue in the 0.1.x series?


Horizontal Scaling

Thanks for the great package!
I had a quick inquiry.  Does this package support horizontal scaling?  I read that the arunoda meteor streams package did not support it, and I need to implement this on more than one Galaxy container in the same app.
If not, are there any suggested ways to implement it?

I've build a sync via mongo to support horizontal scaling in our app. It's not the best eay in my opinion, but it works.

Thanks @maxnowack.  Is there a library you used to do this?  My use of streams doesn't touch the db, so I'm not sure exactly how this would work.

I've just published the code as a npm package :)
https://github.com/maxnowack/meteor-sync-eventemitter

Wow!  Thank you so much!! Perhaps this should be integrated into this package.


#1475 StackingBehavior NEVER hide all buttons

Not complete fix, but it will shown buttons on single line.
Buttons are overlapping and not ellipsized, but better than completely missing buttons...
In sample is added button for testing current behavior.

Version 2.0 is under development as a rewrite, so this will no longer be applicable.


Add more field names?

Would it be possible for you to add more field names? I'm considering using the node-types.json to generate static code definitions of the node structure, but a lot of the rules don't have fields so the resulting data structure would just be a list of other nodes which isn't all that helpful lol. (I'm trying to build a symbol table if it helps.)

Hello,
I am certainly very open to the idea.  Would you be able to suggest a pull request, especially if you have a tool that would kind of help you detect the missing ones.  Ideally the names should match what the AARM uses, though that might not always be possible I think

@briot Do you mean like a list of nodes that don't have fields? That can be retrieved by looking at the node-types.json file. I'd be happy to contribute (along with fixing some things like the pattern for identifiers to match the Ada standard, as well as adding parallel block statements, at least, I think I managed to add them) but I'm uncertain what to name. Do I add field() around the items in choice()? Or just in the sequences? (I ask because I'm still getting used to the tree-sitter API, so I don't know when I should and shouldn't name something.)

We'll have to learn together, as I am also not that familiar with tree-sitter in practice.  All I wanted was syntax highlighting in vim, which I have.  I'd love it if the grammar could be used in more contexts though, so naming nodes definitely looks like it would be nice.  Maybe we can look at specific cases to get a feel for the problem, and decide based upon that

I can already see a situation where this would be useful. Well, two, actually: type declarations/definitions/constraints and expressions. Using the index works, particularly for expressions: expressions, factors, terms, and primaries usually have a left and right-hand side. However, take for example this full_type_declaration:
type Queue is limited interface;
type Node is abstract new Ada.Finalization.Limited_Controlled and Queue with record
   Previous : not null access Node'Class := Node'Unchecked_Access;
   Next     : not null access Node'Class := Node'Unchecked_Access;
end record;

Ignoring the components of the record_definition, this will cause two full_type_declarations to be generated. But here is where my questions arise (and I may just look at different ASTs to figure this out, or maybe write a small AST walker to "tree"-ify the AST so I can understand it easier). The most significant question is: in something like a full_type_declaration, which has an (optional) known_discriminant_part, does that node still get generated as an empty node in the tree, i.e., the tree will be soomething like:

type (reserved word)
Queue (identifier)
null (known_discriminant_part)
is (reserved word)
limited interface (type_definition, but this is hidden)

Or will it appear as:

type (reserved word)
Queue (identifier)
is (reserved word)
limited interface (type_definition, but this is hidden)

If the former, that makes things a lot easier, and we may not need to name anything else at all (though doing so would definitely be useful). But if it's the latter, that complicates a lot, because then I'll need to figure out how to distinguish between when the known_discriminant_part is present or not. I feel like Tree-Sitter might do the former (because this would be sensible behavior) but I'm just not sure. And S-expressions were never my strong suit, so reading the S-expression parse tree makes it difficult for me to mentally model.

@briot Okay, so I just wrote a quick function to walk the tree and output markdown (not the prettiest but...). The indentation helps me visualize the tree in my head. I'd be happy to paste the code here if you like so you can use it yourself. :)
From what I can see, the tree is a bit broken. Take for example the following Ada code (from RosettaCode):
type Queue is limited interface;
procedure Enqueue (Lounge : in out Queue; Item : in out Element) is abstract;
procedure Dequeue (Lounge : in out Queue; Item : in out Element) is abstract;

This file is not actually a valid Ada program: it begins with a full_type_declaration, which from my reading of the grammar cannot appear outside a library_unit_declaration. A compilation_unit can be a library_unit_body or a library_unit_renaming_declaration, with either the library_unit_declaration or library_unit_renaming_declaration preceded by private, but you can't just start a compilation_unit with a type_declaration if I'm understanding things properly.
I'm not sure what to do here. It looks like Tree-Sitter is mis-parsing the file: if you look at the parse tree, it looks something like:

compilation

compilation_unit

full_type_declaration

...

Thought I would let you know about this, I'll look into the grammar to try to figure out why it's doing this (because it shouldn't be).

Okay, so I managed to solve the aforementioned problem. Somewhere in the grammar, change compilation_unit to the following and add the new rules:
        compilation_unit: $ => seq(
            repeat($._context_item),
            choice(
                $.library_item,
                $.subunit
            )
        ),
        library_item: $ => choice(
            seq(optional(reservedWord('private')), choice($._library_unit_declaration, $._library_unit_renaming_declaration)),
            $._library_unit_body
        ),
        _library_unit_declaration: $ => choice($.subprogram_declaration, $.package_declaration, $._generic_declaration, $.generic_instantiation),
        _library_unit_renaming_declaration: $ => choice($.package_renaming_declaration, $.generic_renaming_declaration, $.subprogram_renaming_declaration),
        _library_unit_body: $ => choice($.subprogram_body, $.package_body),
        _context_item: $ => choice($.with_clause, $.use_clause),

This fixes the problem. I would submit a PR but I formatted the file with js-beautify so the diff would essentially show every line of the grammar as being changed in someway. I can still do it though if you like. My modifications do also remove a number of unnecessary conflicts (according to tree-sitter 0.22.6). If you want my version to become the new grammar let me know and I'll open a PR.

I am slightly worried that you might have the wrong expectations here though: tree-sitter doesn't generate a full AST. On purpose, it generates a much simplified tree instead, since its main purpose is for syntax-highlighting / indentation purposes. If you want or need a full AST, you might want to start from libadalang instead.

Your not the only person to recommend I start with that. I'm hesitant to because it requires unconventional tools and methods to actually build it, and it still doesn't support Ada 2022. There sadly are not many other tools/parser generators that can handle Ada's grammar, either, without a lot of refactoring and fiddling with the grammar to make it happy. Other than libadalang (which I couldn't get to build) and this, I don't know a grammar for Ada that is able to actually parse Ada code beyond trivial code that does nothing.
The auto-formatting was something I manually did with js-beautify (I have my own copy of the grammar). I could probably get a somewhat "full" AST out of tree-sitter but you do have a point that it probably isn't designed for that purpose. (There's an Ada grammar I found that does give a full AST, but it generated a parser that was 320MB of C code, so... Yeah, there was no way I was going to use that, especially since it would take ages to compile.) This is one of those times where I wish the specification just resolved all the conflicts and stuff already.. :-(


github: fix job names and IDs for the tests workflow

Flip the incorrect flip that happened in e4baddfad119f0826b22081cb68d29ec47ea5cde

github workflows finished, merging this.


Update nasapaul sample zip file

The blog post I wrote links to zipped files nasapaul.zip and nasapaul2.zip. This naming convention is unclear, and may be confusing to readers. Instead, add ninfo.zip and v.zip to folder /nasapaul. Then update the hyperlink. Then remove the previous zip files.

Task completed.


macOS Big Sur beta - dyld: Library not loaded: @rpath/lib_InternalSwiftSyntaxParser.dylib

In a clean macOS Big Sur beta 5 (20A5364e) installation with also clean Xcode 12 beta installation in an objective-c project, bartycrouch (4.2.0) can neither be loaded correctly by cocoa pods nor after installing via homebrew.
In both cases we receive
dyld: Library not loaded: @rpath/lib_InternalSwiftSyntaxParser.dylib   Referenced from: /usr/local/bin/bartycrouch   Reason: image not found zsh: abort      bartycrouch
The exact same setup on a clear macOS 10.15 Catalina (newest) works.
You had an old issue named the same - but the solution can be excluded as both newest version of bartycrouch and Xcode are used.

New in macOS Big Sur 11 beta, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache. (62986286)

Not quite sure if this might be a thing to check or if its a beta related issue, wanted to let you know.
Might be worth having a look.
Steps to Reproduce the Problem

Install clean macOS Big Sur latest beta
Install latest Xcode 12 beta
Install latest Xcode Command line tools
Open a new project, init cocoa pods with bartycrouch pod or install via home-brew, try to compile or call bartycrouch directly on command line

I had the same issue, found this workaround on another project and solved the problem:

I discovered a similar issue in a library I'm writing. A workaround was to rename Xcode-xyz.app to Xcode.app. It seems there's something in SwiftSyntax that assumes that swift toolchain will be under /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift.

https://github.com/realm/SwiftLint/issues/3105#issuecomment-611136101

This should be fixed with 4.3.0. Please report otherwise if it still happens.

Meanwhile @lechuckcaptain 's solution worked 👍
I will test it. Thank you.

Just ran into this issue with version 4.6.0, Xcode 12.5.1, and macOS 11.4. I tend to have a bunch of Xcode versions installed, all with non-standard names. Creating a symbolic link at /Applications/Xcode.app, as suggested above, seems to work around the problem.


test suite for record layout

record_readme.md explains how the files and runner work. Please read first.
I think the XXXX_test.c file are close to correct. I'm not sure about some of the algorithmic tests on some platforms. I need to dig into it more.
I hacked around on record_runner.zig tons while I was working on layout. It went from an inclusion set of targets to an exclusion set of targets. I won't be insulted if you think it's too janky, but some direction on how to address would be helpful.
Lots of tests work for lots of targets. I'm pleasantly surprised by how many targets work.
@ehaas your changes to for msp430 make that target work on every test except one! nice!

Sorry for being so slow to review this, if this is pr still works I can try to get it merged by the end of the week.

I'm doing some work to clean it up. I'll put up a new PR "soon".

feedback on the readme would be helpful while I'm re-working:
https://github.com/TwoClocks/arocc/blob/record_tests/test/record_readme.md

It seems fine aside from some typos. Also might be better to use 'variable' or something instead of 'static structure'.


Show commits

As of right now, this app only outputs activity on issues and pull requests ... it would be nice to have commits as well (not just in the users repository but also any commits that the user creates)

Of course ... only public contributions 😄

Just realized you opened these issues but I wasn't watching my own repos 😱
So this is how it worked originally, but it became way too dominated by commits. It might just be for me, I tend to make many small commits, but it meant that I wasn't seeing more general information about my activity.

but I wasn't watching my own repos 😱

Yikes 😱

but it became way too dominated by commits ... but it meant that I wasn't seeing more general information about my activity.

Now that I think about it ... I completely agree. Let's leave the tool as is for now.


Write a Swift program to move all zeroes to end of array

Description
Write a Swift program to move all zeroes to end of array
Input  : arr[] = {1, 2, 0, 4, 3, 0, 5, 0};
Output : arr[] = {1, 2, 4, 3, 5, 0, 0, 0};

Input  : arr[] = {1, 2, 0, 0, 0, 3, 6};
Output : arr[] = {1, 2, 3, 6, 0, 0, 0};

How to contribute

Comment !assign to assign this issue to yourself
Fork this repository
Create a new branch
Save the solution in program/program/move-all-zeroes-to-end-of-array/MoveAllZeroesToEndOfArray.swift
Commit the changes
Create a pull request

!assign


Can I config whether open browser automatically?

Issue description
For now if I use this plugin it will open the browser automatically, but I think it would be better to open it when I enter the url. I find viewer.js#L29 has a param openBrowser but not listed in the option of README, I am not sure it will works. Do you have any thought about this?

The option is called openAnalyzer and it's mentioned on the main page.

Sorry,I missed it


Refactor logic for DeriveChild.

There are quite a few edge cases in DeriveChild that need to be considered. This mainly hitches on if a locality has a default context, it MUST be the only context in the locality. Which also means, default and non-default contexts can never be together. This refactors this logic to be more explicit about when a DeriveChild command will be able to satisfy this requirement.

nit: could you run the test_panic_missing test within the caliptra runtime? I highly doubt this change introduces panic, but just want to be sure before merging.

Passing test_panic_missing tests from caliptra-sw


ModuleNotFoundError: No module named 'tensorflow.compat'

Description
Compiled code with imported tensorflow_probability package throws ModuleNotFoundError. The code works as expected if ran directly without nuitka.
Environment
1.0.5
Commercial: None
Python: 3.9.12 (tags/v3.9.12:b28265d, Mar 23 2022, 23:52:46) [MSC v.1929 64 bit (AMD64)]
Flavor: Unknown
Executable: <project_path>\venv\Scripts\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10

The same issue also occured on RHEL.
1.0.5
Commercial: None
Python: 3.9.2 (default, Mar  2 2021, 21:18:39)
Flavor: Unknown
Executable: <project_path>/venv/bin/python
OS: Linux
Arch: x86_64
Distribution: Rhel (based on Fedora) 7.9

requirements.txt:
nuitka==1.0.5
orderedset==2.0.3
tensorflow==2.9.1
tensorflow_probability==0.17.0
numpy==1.21.2

Example code
import numpy as np
import tensorflow as tf
import tensorflow_probability as tfp

print(f"numpy: {np.__version__}")
print(f"tensorflow: {tf.__version__}")
print(f"tensorflow_probability: {tfp.__version__}")

Compilation command
venv\Scripts\python.exe -m nuitka --standalone --enable-plugin=numpy --show-progress --show-scons --lto=no test.py

Compiled program output
2022-08-22 13:55:07.684946: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'cudart64_110.dll'; dlerror: cudart64_110.dll not found
2022-08-22 13:55:07.687204: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.

Failed to import TensorFlow. Please note that TensorFlow is not installed by default when you install TensorFlow Probability. This is so that users can decide whether to install the GPU-enabled TensorFlow package. To use TensorFlow Probability, please install the most recent version of TensorFlow, by following instructions at https://tensorflow.org/install.

Traceback (most recent call last):
  File "C:\Work\random\NUMPY_~1\TEST~1.DIS\test.py", line 3, in <module>
  File "C:\Work\random\NUMPY_~1\TEST~1.DIS\tensorflow_probability\__init__.py", line 20, in <module tensorflow_probability>
  File "C:\Work\random\NUMPY_~1\TEST~1.DIS\tensorflow_probability\substrates\__init__.py", line 17, in <module tensorflow_probability.substrates>
  File "C:\Work\random\NUMPY_~1\TEST~1.DIS\tensorflow_probability\python\__init__.py", line 138, in <module tensorflow_probability.python>
  File "C:\Work\random\NUMPY_~1\TEST~1.DIS\tensorflow_probability\python\internal\lazy_loader.py", line 57, in __dir__
  File "C:\Work\random\NUMPY_~1\TEST~1.DIS\tensorflow_probability\python\internal\lazy_loader.py", line 37, in _load
  File "C:\Work\random\NUMPY_~1\TEST~1.DIS\tensorflow_probability\python\__init__.py", line 38, in _validate_tf_environment
ModuleNotFoundError: No module named 'tensorflow.compat'

What I tried

enable/disable the deprecated tensorflow plugin
enable/disable the anti-bloat plugin
--include-package-data=tensorflow

Neither of that helped

BTW without the tensorflow_probability package, the compiled program works as expected:
2022-08-22 14:53:00.347575: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'cudart64_110.dll'; dlerror: cudart64_110.dll not found
2022-08-22 14:53:00.350148: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
numpy: 1.21.2
tensorflow: 2.9.1

I see, tensorflow_probability will need some implicit dependency love, not done so far.

I have the same problem with tensoflow.compat without the use of tensorflow_probability.
I asue the problem is the protected _api package compat is part of.

This indeed appears to not have to do directly with tensorflow_probability at all, it is somehow an incompatibility with the import mechanism, that I do not get.
This is sufficient to reproduce:
import tensorflow.compat.v1 as tf

It appears that tensorflow should have tensorflow.compat as a variable, that should serve to import v1 from below that module. I could in theory see how the v1 import is then not visible to Nuitka in all cases, but the error is given for the compat that gives this.
I am trying a few variations on the import, e.g. trying .compat on its own and see if that fails already, which would have to mean that something stupid is going on. From there I believe I can get a minimal reproducer. This may after all be a more general issue, although importing compatibility has not been questioned for quite a while now.

Ok, even tensorflow.compat does't work. For once, people have not used a meta path based importer, to achieve strange behaviour, this time, they are extending __path__ in switch __path__ in subpackages depending on how they are loaded.
I think we only need to just set sys.modules["tensorflow.compat"]  for it to work.

Thanks for your report, this is fixed on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html
Feedback if this is working is very welcome, just please do not share plans of doing it, but rather confirmations or denials of it working.
This is also going to be part of the next hotfix for 1.2

I have been compiling for tensorflow_probability and it found more missing modules, and there are also a few hidden dependenies. So while the more API changes are part of 1.2.7 hotfix that I just made, more dependencies are to surface I fear, but with 4000+ modules, it will take a while until this finished I guess, hopefully in time for 1.3 or one of its hotfixes.

I got quite a bit done, but this is not immediately obvious:
  File "C:\Users\kayha\repos\Py2C\MINITE~1.DIS\tensorflow_probability\python\distributions\__init__.py", line 161, in <module tensorflow_probability.python.distributions>
  File "C:\Users\kayha\repos\Py2C\MINITE~1.DIS\tensorflow_probability\python\distributions\kullback_leibler.py", line 269, in augment_kl_xent_docs
  File "C:\Users\kayha\repos\Py2C\MINITE~1.DIS\tensorflow_probability\python\distributions\kullback_leibler.py", line 261, in merge_doc
AttributeError: 'NoneType' object has no attribute 'split'

Apparently some doc strings are None which is not expected. Need to check what is going on there later.

The tensorflow.compat work is part of the current pre-release.

The 1.3 release has been made. However tensorflow_probability will need more work, still the original report is kind of addressed, so I am closing this and will work on that package offline when and if time permits.


Processing but no download

Seems those pesky folks are at it again lol.
I want to say thank you for putting this out for the community to use. Some of us I know use the .midis from Musescore to play music in Final Fantasy 14. We do it for fun, and the enjoyment of others and enjoyment of music. Thank you for helping us spread joy in these stressful times :)

Can confirm. However I can download .bin files from the mcsz button, and the Music XML and Individual Part buttons open an about:blank page that says "Processing". This may however, be due to me using Firefox for Android. The saddest part is that I discovered this yesterday, and it worked yesterday. Today it stopped working. Perfect timing Ultimate Guitar.

try again with the latest version

try again with the latest version

Works now, thank you.

Seems they are keeping up with your progress. Getting the processing error again with 15.8 now.

Can confirm. Same exact characteristics as previously.

fixed in  v0.15.9

fixed in  v0.15.9

I don't know how you have the patience to keep updating this several times per day, but you sir are truly the best

For real man. Thank you. Sorry to spam this issue, but thank you from the bottom of my heart, and everyone else I know that uses it.

I cannot download mp3

I cannot download .mp3 files
It will have a pop up saying "processing..."

10 minutes and nothing happened

If it doesn't work, always try Individual Parts

There is no mp3

There is no mp3

https://en.wikipedia.org/wiki/FLAC
https://en.wikipedia.org/wiki/Ogg_Vorbis
MP3 is a very old format.
Those file formats are chosen over MP3 since FLAC can provide better sound quality (lossless), and OGG Vorbis can provide better data compression.
The most important thing is that MP3 is not fully open-source and royalty-free.

I see, it just confuses me why there is an MP3 option but not used

I see, it just confuses me why there is an MP3 option but not used

It is being used. If you can't tell or if you haven't taken the time to read the very issue thread you've replied to, MuseScore is currently updating their website to stop this script from working. Normally, all options should work, but it is very difficult to make everything work when the website is changing every few hours.

I see.   A musescore dev even responded to many complaints in an issue here. It got pretty heated. You can find the threads in talking about easily but I'm too tired to link them

They really must see this as a threat. If only they got rid of the 20 per day limit, they'd probably get alot more people keeping their pro subs.

Did they just update?

If only they got rid of the 20 per day limit, they'd probably get alot more people keeping their pro subs.

so everyone can download all MSCZ files, and create every mirror site.


Fix for issue #7

Thanks for your detailed issue and the pull request!
After checking your code I found a more general solution by using the appropriate method of LibreOffice for converting the file path. That should solve the issue and we can get rid of both calls of the replace() method. I just pushed the change to the repo (1688dfef2d2cfbaf85dfe19c5b68ddc523f778c6).
I would appreciate it if you could test whether the change solves the issue #7 and report back.


change the content of subject and body by email sharing action

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind api-change
/kind backend-change
/kind ui-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Email sharing on hash in action page is not correct
Which issue(s) this PR fixes:

Fixes #594
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

The link in the email content is currently not clickable and needs to be copied to the browser's address bar.
The discussion can be found here


For EmptyContract payable could be generally removed

So my understanding of EmptyContract is that this contract is put into some system contracts by default. Could you quickly elaborate on "some"?
What I don't understand is why you make it payable. There could be some users trying (for whatever) reason to send ETH to one of those contracts. Right now these contracts can receive ETH and this could be prevented, however (an additional guardrail). It makes sense in one case where you define a system address as a burn address, but not generally IMHO. My recommendation would be to remove the receive function completely and define a non-payable fallback function, except for the burn address.
// SPDX-License-Identifier: MIT

pragma solidity ^0.8.0;

/**
 * @author Matter Labs
 * @notice The "empty" contract that is put into some system contracts by default.
 * @dev The bytecode of the contract is set by default for all addresses for which no other bytecodes are deployed.
 */
contract EmptyContract {
    fallback() external {}
}

So if I understood your answer correctly there should be two versions of EmptyContract: a payable and a nonpayable version. This should be part of the codebase imho.

Now I understand :-D - thanks for elaborating.


What if this pivoted to scan your repos and give you tips, based on the data available.

Taking the insights from DORA and other DevOps research and applying them to a target repository.
For example,

your tests run for longer than 10 minutes. (DORA)
your lead time for changes and MTTR are very different - typically you expect them to be equivalent
low frequency of commits (https://www.youtube.com/watch?v=cRJZldsHS3c) - (be careful, this is easy to game and doesn't test quality of commits)

Not right for here, now. Closing.


(python3) cygdb not found

Chocolatey Version
1.1.0
Chocolatey License
No response
Package Version
3.10.4
Current Behaviour
Can not install Cython, cygdb.exe not found

Expected Behaviour
No response
Steps To Reproduce

Create a new Windows 10/11 Virtual Machine
install choco
run choco install python
run pip install Cython

Environment
- Operating System 1: Windows 10 Pro x64 21H2 19044.1645
- Operating System 2: Windows 11 Enterprise x64 21H2 22000.556
- PowerShell Version: pwsh 7.2.3 x64

Chocolatey Log
https://gist.github.com/kouhe3/a71b2a0979a4c0db251d77e382b469c3

Anything else?
If i use winget , instead of choco.
winget install --id=Python.Python.3  -e.
no problem

On Chocolatey the python directory is locked down, so it can not be written to by a normal user and requires an elevated shell when calling pip.
It sounds like you are trying to install Cython while running in a non-elevated shell, which by design won't allow the package files to be written to disk.
Can you try again while calling pip in an elevated shell?

yes. You are right . pip install work in elevated shell.
I tried to install jupyter in non-elevated shell , and had the same problem.
ERROR: Could not install packages due to an OSError: [WinError 2] can not found 'C:\\Python310\\Scripts\\send2trash.exe' -> 'C:\\Python310\\Scripts\\send2trash.exe.deleteme'
but in elevated shell , I can install jupyter.
What is the difference between python installed by choco  and winget ?

If I use choco to install python, will I need admin shell for every pip install in the future? 🤔

What is the difference between python installed by choco and winget ?

To be completely honest, I do not know as I haven't checked how they are doing it in winget.
What I can say though, if the user do not install python3 to their own custom directory the entire folder will be locked down to admins only (this was in response to a abuse report we got a few years ago). If you uninstall python3 and then install it again while specifying the package parameter /NoLockdown then the folder will not be locked down to admins only (if you do not have the feature useRememberedArgumentsForUpgrades also enabled you need to specify that parameter on upgrades as well).
Do note that package parameters can not be passed in if you are installing through the python meta package, only if you install python3 package directly.

If I use choco to install python, will I need admin shell for every pip install in the future? 🤔

If you just install it and upgrade python3 package without specifying the nolockdown parameter, then yes. You will need to use admin shell every time.
Since this is working as intended in this case, I will be closing this issue as there is work around to also not make it admin only installations.

Lastly, just as a reference.
See the available package parameters on the description of the python3 package here: https://community.chocolatey.org/packages/python3