ERR_INVALID_ARG_TYPE on attempting to start

Describe the bug
After fresh installing both npm and alacritty-themes, I get the following error when attempting to run the alacritty-themes command
PS C:\> alacritty-themes
node:internal/validators:119
    throw new ERR_INVALID_ARG_TYPE(name, 'string', value);
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at new NodeError (node:internal/errors:371:5)
    at validateString (node:internal/validators:119:11)
    at Object.join (node:path:429:7)
    at possibleLocations (C:\Users\[redacted]\AppData\Roaming\npm\node_modules\alacritty-themes\src\helpers\index.js:74:10)
    at Object.<anonymous> (C:\Users\[redacted]\AppData\Roaming\npm\node_modules\alacritty-themes\src\helpers\index.js:7:5)
    at Module._compile (node:internal/modules/cjs/loader:1095:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1147:10)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:999:19) {
  code: 'ERR_INVALID_ARG_TYPE'
}

Node.js v17.0.1

Steps to reproduce the behavior: simply attempt to run alacritty-themes

Installation

I installed it via npm i -g alacritty-themes (global installation)

Run alacritty-themes

[ x ] Did you add params? yes, I type "alacritty-themes Ayu-Dark"
[ x ] Did you add params? no, I just type "alacritty-themes" then click up/down keys

Neither works, same error.
Operative System:
Windows 10 Home 19043.1348

I'd like to have your help to validate this package works on Windows I haven't had the chance to test it there, I already added a PR #68 with the possible fix to this problem, but you could have more...

@leslaron thank you for opening the issue. would you please update your global package to the last version and try again.
I'd like to have your help to validate this package works on Windows I haven't had the chance to test it there.

So with the new update I get a different error which is as follows:

PS C:\> alacritty-themes
C:\Users\[redacted]\AppData\Roaming\npm\node_modules\alacritty-themes\index.js:18
    throw NoAlacrittyFileFoundError;
    ^

Error: No Alacritty configuration file found. Expected one of the following files to exist:
C:\Users\[redacted]\AppData\Roaming\alacritty\alacritty.yml
    at Object.<anonymous> (C:\Users\[redacted]\AppData\Roaming\npm\node_modules\alacritty-themes\src\helpers\index.js:5:35)
    at Module._compile (node:internal/modules/cjs/loader:1095:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1147:10)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (C:\Users\[redacted]\AppData\Roaming\npm\node_modules\alacritty-themes\bin\cli.js:8:26)
    at Module._compile (node:internal/modules/cjs/loader:1095:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1147:10)

The alacritty folder was not created upon a fresh install, however by manually creating both the folder and the yml file in appdata\roaming, the themes now seem to work just fine.

Yes, we don't create the alacritty.yml file unless you required typing the alacritty-themes --create command
I don't understand how windows manage the folders, where did you create the folder and alacritty.yml file?
appdata\roaming is after your personal path? I mean Users/my_user\appdata\roaming or what is the full path?
Could you give me a favor? would you test the alacritty-themes --create command, please?

Yes, we don't create the alacritty.yml file unless you required typing the alacritty-themes --create command
I don't understand how windows manage the folders, where did you create the folder and alacritty.yml file? appdata\roaming is after your personal path? I mean Users/my_user\appdata\roaming or what is the full path?
Could you give me a favor? would you test the alacritty-themes --create command, please?
Also, In good news it's working now!, you can close the issue if you feel it's solved, please

PS C:\> npm uninstall -g alacritty-themes

removed 20 packages, and audited 1 package in 624ms

found 0 vulnerabilities
PS C:\> npm i -g alacritty-themes

added 20 packages, and audited 21 packages in 4s

1 package is looking for funding
  run `npm fund` for details

found 0 vulnerabilities
PS C:\> alacritty-themes --create
The alacritty.yml config file was created here C:\Users\my_username\AppData\Roaming\alacritty\alacritty.yml
PS C:\> alacritty-themes
√ Select a theme » Baskerville - Count Von Count
The theme "Count Von Count" has been applied successfully!
PS C:\>

@JuanVqz I missed the --create command, and that solved it entirely. Can that not be run on install? Anyways, issue resolved. As for the install location, I hope the above can help with that.


Vulnerability roundup 95: php-7.2.32: 2 advisories [6.5]

search, files

[ ] CVE-2020-7069 CVSSv3=6.5 (nixos-20.03)
[ ] CVE-2020-7070 CVSSv3=5.3 (nixos-20.03)

Scanned versions: nixos-20.03: d3784204ba1.
Cc @etu
Cc @globin

See also: #99823, #93253

Merged - so close.
also...
20.03 is Frozen and EOL.
As such, issue is closed.


[Suggestion:] Device ID/Client ID bans

Is your feature request related to a problem? Please describe.
Bans are quite easy to evade by using VPNs and alt accounts.
Describe the solution you'd like
Using device IDs and client IDs to ban players.
Describe alternatives you've considered
None
Additional context
None

Good suggestion. I'll add it in one of the next versions.

ClientID's can be be changed by the user. But I can add DeviceID banning.

ClientID's can be be changed by the user. But I can add DeviceID banning.

They both can be changed but you can't change them on mobile devices as far as I'm aware and doing so is a fairly involved process on Windows.


provider path notation cannot access objects who's names start with the path separator

Steps to reproduce
function \hello {echo hello}
get-content function:\hello

Expected behavior
echo hello

Actual behavior
get-content : Cannot find path 'Function:\hello' because it does not exist.
At line:1 char:1
+ get-content function:\hello
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (Function:\hello:String) [Get-Content], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetContentCommand

This seems to affect all provider path constructs, where the provider doesn't actually have a navigable hierarchy, (function:, and variable:) and that the '\' character is a valid character.  I also tested using a / and on Windows I got the same behavior.  It only seems to affect if that character is used in the first position of the objects name.  (hello\ works as expected)
I couldn't seem to locate a means to escape the leading slash, such as can be done with wildcard operators. (EDIT: while it seems to depend on the exact application, either \\ or \\\ has been found to work as an escape, but its not consistent, and doesn't work with wildcards)

This also fails to work:
dir function:?h*

It will find other variations, but not items to which the ? could match either \ or /.

Try get-content function:\\hello and ${function:\\hello}.
Indeed, Get-Childitem and Get-Item apparently cannot find such a function name with wildcards, though Get-Item -Path function:\\hello works - though, curiously, Get-item -LiteralPath function:\\hello doesn't.

Try get-content function:\\hello and ${function:\\hello}.

Neither work, all the leading \ are removed in the error response from 'get-content'.
Doubling of : is needed, but doesn't work for \ or /.
I cannot get the Get-Item -Path function:\\hello to work either.  It errors that the path does not exist.   just dir function: shows that its there, but any attempt to match it fails.

@mklement0 did you mean get-childitem works …   just tried dir function:\\hello and that worked.  Pretty sure dir is get-childitem.

Yes, dir is Get-ChildItem - best to call cmdlets by their real name here.
I assumed that Get-Item and Get-ChildItem behave the same in this case, which is generally true with non-container items - though I now see that  with Get-ChildItem -LiteralPath function:\\hello does work (on macOS and Linux - see next point).
I just realized that my previous examples work on macOS and Linux only; on Windows you need to throw in an additional \; e.g., Get-Item function:\\\hello - except with Get-ChildItem -LiteralPath.
I think it's fair to conclude we have a mess on our hands.

I can confirm that on Windows, ${function:\\\hello} does work.  The first one gets 'root' and the next two form an escape?  Get-Item works the same way.  Get-ChildItem only needs two \.   I can get Get-Content to work only if I pipe the result from Get-Item to it. (gi function:\\\hello | gc)
One would expect the provider: notation to work fairly consistently, in particular where in each situation they are an 'argument' (to almost identical commands)  I don't even remember how I stumbled upon this in the first place.  I am sure it had to do with testing what were acceptable first characters.

One would expect the provider: notation to work fairly consistently

Hear, hear.
Taking a step back:

You could argue that non-hierarchical providers should never need a path separator at all.

You could argue that \ should never have been allowed as a legal char. in function names (and other identifiers) - flexibility is nice, but such permissiveness can lead to conceptual confusion and - clearly - technical problems too.

I just stumbled upon something I failed to look at earlier.
the path function::\hello works in all invocations so far.  It is consistent.
I realized this because that's what PSPATH results in when other variations worked in get-childitem and get-item.
Is this a lack in documentation, that the : is supposed to be intentionally doubled?

Good find, @msftrncs. I personally have never seen the :: in this context.
Note that Get-Item function::\hell* (wildcards) still doesn't work, however; ditto with Get-ChildItem.

Wildcards work, if the offending character is wildcard'd, ie get-childitem function::?hel*.

recap:

function:: is a provider notation.
function: is a drive notation
The function provider implements the function: drive.
PowerShell translates drive paths to provider paths with logic that doesn't work for providers that don't actually support hierarchy.  And this translation seems to be implemented with some inconsistency by different commands.
the 'function::' provider notation still has some issues resolving wildcards, probably because the wildcard provider is still expecting paths with hierarchy separators.

Perhaps we could resolve this by limiting chars which can be used in names. It seems we discussed this previously.


what is the status of v3

if I'm starting  a new project, should I use v2 stable or v3 ?

I'm using v3 :) Pretty stable now..

great - is that the one on the /dev branch ?

yes, dev is v3. We will likely be pushing a release "Soon".


Changed byte to int for prefix_length_key

Description
Lucene's TruncateTokenFilterFactory.java has prefixLength as byte but the class TruncateTokenFilter.java reads it as int. So to make the behavior consistent changed the byte to int in the factory and added a test case for the same.
#12449
Any length greater than 127 given would be accepted in TruncateTokenFilter but not in TruncateTokenFilterFactory. An exception is thrown due to parsing error from Byte.parseByte method.

What a mess! Thanks for fixing.


play-core failing in 2.13.x build

it's probably not 2.13 specific, probably the 2.12 would be failing too if it weren't broken for other reasons
[play-core] [error] /home/jenkins/workspace/scala-2.13.x-integrate-community-build/target-0.9.7-RC1/project-builds/play-core-1c5a6cad40a4c451d7786223e94f3eeb7df24e5d/framework/src/play/src/main/scala/play/api/http/Writeable.scala:95: value toBytes is not a member of object play.api.libs.json.Json
[play-core] [error]     Writeable(a => ByteString(Json.toBytes(a)))
[play-core] [error]                                    ^
[play-core] [error] one error found

@wsargent does this look like the usual kind of thing where the various Play repos are just a bit out of sync with each other and it will probably be fixed before long...?

Looking -- this seems to be coming from Play-JSON -- shows up in master:
https://github.com/playframework/play-json/blob/master/play-json/shared/src/main/scala/Json.scala#L68
Shows up in M2:
https://github.com/playframework/play-json/blob/2.6.0-M2/play-json/shared/src/main/scala/Json.scala#L68
Does not show up in M1:
https://github.com/playframework/play-json/blob/2.6.0-M1/play-json/src/main/scala/play/api/libs/json/Json.scala#L68
My guess is that you have an M1 dependency :-) /cc @gmethvin

yes, we are frozen at M1, but that's because play-ws requires M1. can play-ws be upgraded?

considering this at a higher level, perhaps it would be better if I just froze all of the Play repos at fixed versions in the community build. it really isn't the purpose of the community build to be plan A for catching this kind of thing; it ought to be plan B, or actually plan Z.

I can fix the dependencies.  Sorry, we're moving around a bunch of stuff right now.

verified that this also fails in the 2.12.x community build (with version=2.12.1 ./run.sh)

Should be fixed via https://github.com/playframework/play-ws/pull/78

sweet, sweet green:
[info] Project play-core---------------: SUCCESS (project rebuilt ok)
[info] Project play-json---------------: SUCCESS (project rebuilt ok)
[info] Project play-ws-----------------: SUCCESS (project rebuilt ok)

thank you @wsargent @cchantep!


🖌 style: UI update (dark theme)

Summary
numerous styles have been corrected for the dark theme. This latest style update has significantly enhanced the accessibility of LibreChat in dark mode
Change Type

[x] Style

Checklist

[x] My code adheres to this project's style guidelines
[x] I have performed a self-review of my own code
[x] I have commented in any complex areas of my code
[x] My changes do not introduce new warnings
[x] Local unit tests pass with my changes

Hi @Berry-13
Thanks for this. Please resolve the conflicts so I can review.

Hi @Berry-13
Thanks for this. Please resolve the conflicts so I can review.

done


[KOGITO-4110] - Single namespaced operator reacts on CRs created in d…

…ifferent namespaces
See: https://issues.redhat.com/browse/KOGITO-4110
Signed-off-by: Tarun Khandelwal<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

The issue should also be available in 1.1.0 when we release, not sure if we should cherry-pick this or maybe mark it as known-issues in 1.1.0.

The issue should also be available in 1.1.0 when we release, not sure if we should cherry-pick this or maybe mark it as known-issues in 1.1.0.

@Kaitou786 I guess the change would be easy to cherry-pick to 1.1.x.
Kogito 1.1.0 will be released once Quarkus 1.11 is available so I guess we have some days to test this. and the whole weekend for nightly to run so there is any problem, we can still revert on Monday.
wdyt ?

@Kaitou786 I guess the change would be easy to cherry-pick to 1.1.x.
Kogito 1.1.0 will be released once Quarkus 1.11 is available so I guess we have some days to test this. and the whole weekend for nightly to run so there is any problem, we can still revert on Monday.
wdyt ?

Yeah, that sounds good to me. Let me cherry-pick it to 1.1.x :)

Yeah, that sounds good to me. Let me cherry-pick it to 1.1.x :)

/jenkins test

/jenkins test

@Kaitou786 You should rebase so that it works on AWS (because of buildahnot supported anymore by Quarkus ...)

@Kaitou786 You should rebase so that it works on AWS (because of buildahnot supported anymore by Quarkus ...)

/jenkins test

/jenkins test

/jenkins test

/jenkins test

The error is not related to this PR. @Kaitou786 @sutaakar is there a workaround for this DMN error?

The error is not related to this PR. @Kaitou786 @sutaakar is there a workaround for this DMN error?

the error is almost resolved. https://github.com/kiegroup/kogito-cloud-operator/pull/714 should be merged once ok

the error is almost resolved. https://github.com/kiegroup/kogito-cloud-operator/pull/714 should be merged once ok

/jenkins test

/jenkins test

/jenkins test

/jenkins test


Don't trigger TextYankPost on X external selections

Due to how Xorg clipboards work clip_get_selection is be called
whenever another client requests the clipboard content owned by Vim.
Prevent the emission of autocmds when the yank operation is triggered by
some external mechanism, this avoids nasty side-effects such as #4201
beside stopping the emission of spurious TextYankPost events.
A test case to make sure a TextYankPost is triggered when the visual
selection is left (and cb=autoselect or cb=autoselectplus) is also added
to prevent this feature from regressing.
Closes #4201

It appears the test fails on MS-Windows.

Hmm, no idea why it's failing only on Windows. clip_auto_select should be called anyway and the TextYankPost event triggered but that's not the case here :
I don't have a Windows box to test this though...

Ok, I think I figured out what the problem is.
end_visual_mode doesn't ever call clip_auto_start because on Windows (and QNX and Haiku, but not on macos and X11) clip_mch_own_selection is always returning FALSE, thus clip_star.owned is always false.
Let's see if this alternative approach is better, the phantom yanks from clipboard.c don't emit any autocmd, we do so in end_visual_mode instead.


JAMES-3784 Ease mail repository / event dead letter operation

Jira: https://issues.apache.org/jira/projects/JAMES/issues/JAMES-3784

11:08:53,643 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (check-style) on project james-server-webadmin-mailrepository: You have 2 Checkstyle violations. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (check-style) on project james-server-webadmin-mailrepository: You have 2 Checkstyle violations.

Squash fixup & Complete TODO

You can rebase it again (sorry) as I just merged https://github.com/apache/james-project/pull/1049


Physics2D change

Fix 0 mass error for a Collider2D without a PhysicComponent2D
Remove ColliderID overwrite for CompoundCollider2D

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


DBZ-1814 (binary handling mode)

https://issues.redhat.com/browse/DBZ-1814
Supersedes https://github.com/debezium/debezium/pull/1516/.
@jpechane, could you review this one, in particular my amendments? Thanks!

@jpechane, just force-pushed to fix a test failure.

Rebased onto the DBZ-2033 branch, so to benefit from the test stablization done in that branch.

@gunnarmorling I did look into the PostgreSQL specific code and it looks good.
I'll test this PR to see if addresses the concerns raised in https://issues.redhat.com/browse/DBZ-1266 but the tests look good and I think it should not be an issue.
Has a purely hypothetical question though, the current switching on BinaryHandlingMode doesn't allow for custom implementations but it shouldn't be an issue since I personally can't think of any other conversion I would've done apart from the ones already implemented.
Custom may be useful if somebody has added their own custom data types into PostgreSQL and can implement a matching Java type to return as but I really hope nobody went to those lengths.

Reviewing, unfortunately this PR now requires rebase due to docs conflicts

Thanks for reviewing, @hashhar!

the current switching on BinaryHandlingMode doesn't allow for custom implementations but it shouldn't be an issue since I personally can't think of any other conversion I would've done apart from the ones already implemented.

Yeah, I don't think that's needed either.

Custom may be useful if somebody has added their own custom data types into PostgreSQL and can implement a matching Java type to return as but I really hope nobody went to those lengths.

In that case they should be using the converter API that was recently added. The "unknown types" option is generally a measure of last resort, i.e. people should preferably use converters and/or send PRs for adding more type support to Debezium proper.

Rebased and force-pushed.

@gunnarmorling Last question, as this is a common connector feature why is it unavalibale to other connectors like SQL Server?

why is it unavalibale to other connectors like SQL Server?

Good point, largely a question of getting done with it. I've logged https://issues.redhat.com/browse/DBZ-2155 as a follow-up.

@jfinzel @gunnarmorling Applied, thanks a lot!


[RFC] Ambiguity in the File namespace API

Motivated by #13849, I started looking at uses of  File.file? and similar methods. That issue was about an inadequate use of that method in the compiler. Sadly, it doesn't look great on other call sites as well. The problem is systematic and asks for improvements on the API level.
Introduction
File.file? seems like a reasonable choice for checking if a path is a file. But it depends on the understanding of "file". This methods considers an (ordinary) file in contrast to other file types like directory, special device file, named pipe. This detail is often not terribly relevant. Most use cases shouldn't worry too much about the exact type.
But often doesn't mean always and rare usage of some of these types makes it easy to miss any shortcomings on them.
A typical intention is to verify that File.read or similar would work on the path. But that's not what File.file? does. It's focused on entry types in the file system. Named pipes or character devices work for File.read as well and their exclusion is often unreasonable and unintended.
File.exists? is confusing because File.exists?(path) suggests it's checking if a file exists. But this method checks if anything exists at the path. It doesn't need to be a file. It can be a directory.
It get's even more confusing. The following example seems legit and safe. But in reality, it doesn't make any sense:
if File.readable?(path)
  File.read(path)
end

Despite the similar name suggesting a relation, File.readable? has nothing to do with File.read.
File.readable? is typically true for a directory[^1]. But File.read does not work on directories.
I've mentioned these shortcomings in my talk at CrystalConf 2023. This issue however is a more complete and organized collection on this topic.
[^1]: The readable bit is typically set on directories because that enables listing its entries.
Investigation
I looked through stdlib and compiler sources for call sites of some related methods in the File namespace.

File.file?, File.directory?, File.symlink? check whether the file is of the respective type (see File::Type)
File.readable?, File.writable? and File.executable? check if the process has the rights to read/write/execute a file.
File.exists? checks the existence of a file entry, but not its type or access rights.

Some of the findings from combing through stdlib and compiler sources
The most severe faults that I noticed, have already been fixed:

#13937
#13760
#13869
#13896

Some examples for lesser issues where there was lesser need to fix them directly:
https://github.com/crystal-lang/crystal/blob/6b9ad16c98f0289a90a6cc74493a83898050af6f/src/compiler/crystal/command.cr#L127
https://github.com/crystal-lang/crystal/blob/6b9ad16c98f0289a90a6cc74493a83898050af6f/src/compiler/crystal/command.cr#L545
These are similar to #13849 (same location) and should actually check if the path points to something that we can practically read from.
There are many more similar instances in the compiler that I'm skipping for brevity. They're usually related to loading source code or cached data from files. In some cases it might be fine to use File.file?, but in others the same limitations as above apply.
https://github.com/crystal-lang/crystal/blob/6b9ad16c98f0289a90a6cc74493a83898050af6f/src/crystal/system/unix/time.cr#L124
This goes the extra step of also checking File.readable?. But its still limited to ordinary files.
https://github.com/crystal-lang/crystal/blob/6b9ad16c98f0289a90a6cc74493a83898050af6f/src/time/location/loader.cr#L95
This goes another step extra and over the top. File.exists? is redundant to File.file?.

There are plenty uses of these methods that are dramatically wrong, others not that much. For some of these methods, their semantics rarely match the apparent intention at the callsite. I barely found any instance where I'm confident that the method corresponds exactly to the intended purpose.
It seems very clear that there are many issues with utilizing these API methods in the standard library and compiler. It's not hard to extrapolate that this would apply to other code bases as well. We can't even get it right in the stdlib!
An easy solution would be if people just read the documentation. It clearly says what these methods do!
But the sheer scale of inapproriate usage clearly points to intrinsical flaws. It's hardly possible to use these methods correctly for the most common use cases
It's not that they're completely useless, they have their purpose. But those are specific niche use cases.
You won't need them unless your Crystal program explicitly deals with file system details, for example.
Analysis
I don't think any of these individual methods are wrong in some sense.
The underlying problem is an ambiguous mixture of different concepts in the same namespace.
Some methods are tightly coupled to the tiny details of the file system and do not match the scope of higher-level, usage-oriented APIs.
Different understandigns of the term "file" in methods from the File namespace:

File.file?: only an ordinary file (excluding named pipes and character devices)
File.read: ordinary files, named pipe and character device
File.exists?: any kind of entry in the file system, including directories

Having that all crowded together in the prominent top-level File namespace seems to be the cause for most misunderstandings.
Discussion
I believe we should separate methods with different scopes to express their differences more clearly.
Lower-level methods using the narrower definitions (e.g. .readable?, .writable? and .executable?) could fit into File::Info or File::Type. Their use cases are rare and there's not much reason to have them in a high-level namespace.
The File type is focused on the concept of a stream that can read and write. So the File class namespace should be reserved for the core of methods with that middle definition.
It could use a set of methods that check wether a read or write operation should principally work on a given path. Maybe File.can_read? and File.can_write? could work.
I'm not sure what to do about the wider definition. There's no apparent target for that. Maybe we should consider a new FileSystem namspace? Path could be an option, but it has so far been understood in an abstract sense, so we might just be heading for another mixture of concerns.
I think most methods of this scope are not even that bad to mix in the File namespace. Except for .exists? I've found little cause for confusion. This might need some more investigation, but perhaps we could leave them in the File namespace and just rename File.exists? to a less ambiguous name.

I was curious after reading this so I took a quick look at what other non-Ruby languages do for these types of file APIs.
Interestingly enough it seems like Python, Go and C++ lack a high-level file permissions API like Crystal has currently with File.readable?, File.writable? and File.executable?. Basically the idea is that if you really need file permissions info you can go the some sort of lower level API like stat. This seems similar to what Crystal already does with File::Info. Python and Go even seem to suggest just assuming that files have the permissions you expect and just handle the errors as they pop up.
The File.exists? method is interesting because it's not consistently implemented for different programming languages. Ruby, Crystal, C++ and Python all have it while Go and Node don't have it. In fact, Node used to have it but it got deprecated at some point (see docs).
Looking over the documentation for a few languages made me realize that the Crystal docs tend to not clarify the difference between file system objects and individual file types very well.

File.exists?
Ruby

Return true if the named file exists.
file_name can be an IO object.
“file exists” means that stat() or fstat() system call is successful.

Python

Return True if path refers to an existing path or an open file descriptor. Returns False for broken symbolic links. On some platforms, this function may return False if permission is not granted to execute os.stat() on the requested file, even if the path physically exists.

Crystal

Returns whether the file given by path exists.
Symbolic links are dereferenced, possibly recursively. Returns false if a symbolic link refers to a non-existent file.

File.file?
Ruby

Returns true if the named file exists and is a regular file.
file can be an IO object.
If the file argument is a symbolic link, it will resolve the symbolic link and use the file referenced by the link.

Crystal

Returns true if given path exists and is a file.

it seems like Python, Go and C++ lack a high-level file permissions API like Crystal has currently with File.readable?, File.writable? and File.executable?. Basically the idea is that if you really need file permissions info you can go the some sort of lower level API like stat. This seems similar to what Crystal already does with File::Info.

Yeah, I think that's quite reasonable considering that valid use cases for these methods are quite rare.
Note that stat does not have this level of information. It only has the basic file permissions (not ACL or correlation with user/group). Thus File::Info in Crystal (which is based on stat) currently does not entail this either.

Python and Go even seem to suggest just assuming that files have the permissions you expect and just handle the errors as they pop up.

That's probably a good choice in many use cases. Even if you do every possible check beforehand, File.read may still fail for various reasons. Maybe limitations in the file system driver. So the only way you can reliably know whether File.read will work is actually running it.  There's usually no need to address different error conditions explicitly.

When doing things with actual files and directories, I like being able to build it up with Path
dir = Path['mydir']
file = dir / 'myfile'

I wish, like ruby Pathname we had the file? and directory? methods on Path and maybe even mkdir on dir Path's
Dir.mkdir dir unless dir.directory?
or
dir.mkdir_p unless dir.directory?

@dsisnero I think enhancements to Path are really not within the scope of this issue.
There has been a bit of a debate about whether Path should be aware of any actual file system information or stay purely abstract. It would probably be best to start a discussion about this on https://forum.crystal-lang.org
Thanks.

@straight-shoota I think extending Path to become concrete is in scope of this issue.
For example Path.exists? wouldn't be ambiguous anymore. Other methods would make sense on Path (both as class and instance methods). We can also use the opportunity to lift some ambiguities (e.g. .file?).

This is certainly related but IMO is should be a separate discussion. The outcome affects parts of this discussion, of course. But it's not fundamental, it just offers one potential solution for one of the aspects (and it's the least important one). The more critical issues of this topic do not depend on the Path discussion.

From the above analysis:

I'd be fine dropping readable?, .writable? and .executable? altogether, but maybe someone would like them (e.g. to implement ls) so I guess we could move them to File::Info since permissions are part of the file metadata (and not the actual data).
You said there aren't reliable ways to know whether we really can actually read, write or execute a file because of ACL and others, let's avoid this.
IMO Path is the way forward, it's already not fully abstract anyway: Path.new is OS dependent, Path#expand supports the home directory, ...

You said there aren't reliable ways to know whether we really can actually read, write or execute a file because of ACL and others, let's avoid this.

There's no reliably way to know for sure. But there are simple ways to tell that you can't. And I think this is actually quite valuable for a number of use cases (I list some examples in the detailed investigation report).
And IMO it's better to do a basic sanity check before the read/write/exec than just perform it and then deal with any errors. Compare the following examples for optionally reading from a file if it exists.
begin
  File.read(path)
rescue exc : FileNotFoundError
  # ignore error if file doesn't exist
end

if File.readable?(path) && !File.directory?(path)
  File.read(path)
end

Note: The examples don't do exactly the same thing and there are more error cases not covered for brevity. This fact also exemplifies that it's a complex topic that needs attention to get the semantics right.
I think the latter form is more ergonomical and efficient. However the condition readable &&! directory isn't very straightforward. So UX could be improved by providing direct predicate methods for this kind of test.

I'd suggest File.can?(permissions, path) where permissions is a flag enum.

Hm. I see how that could be useful. But I think it's not as easy to use and could be confusing (there's already File::Permissions enum, for example).
If you need more detailed information, it's probably better to employ the lower level File::Info API directly.
My idea with .can_read? etc. is to be easy to discover and convenient for the most common use cases.

An alternative to query methods such as .can_read? could be having alternatives for the methods that would be guarded by them, which handle these error cases internally and ignore them. This would result in a most trivial API and isn't succeptible to race conditions.
For example, File.read? would return nil if the file does not exist.
It would be the same concept as File.info and File.info?.
An issue with this approach is that it's not possible to easily distinguish between a path not existing at all or being of a wrong kind (like a directory). But I'm not sure if that's actually that much relevant. I presume if you want to read from a specific file name, it's okay if it does not exist, but if it's something entirely different, that's probably a odd situation that needs attention.


fix unwinding exceptions that push FPU registers onto the stack

the correct value of constant EXC_RETURN_MARKER is 0xFFFF_FFE0 but the value was typo-ed in the
refactor part of PR #163 #203
https://github.com/knurling-rs/probe-run/commit/226c6930dbcd0def0acb2dc51d0584a291c2f2bf#diff-42cb6807ad74b3e201c5a7ca98b911c5fa08380e942be6e4ac5807f8377f87fcL755

Okay no wonder I didn't see this during review :laughing:
bors r+


Change Field vgrid metadata in MAPL3

Currently in MAPL3 the following information is stored about vertical structure of a field:

num levels of grid (i.e., not of the field itself)
vloc (staggering)

The following change should be implemented:

Field should store the number of levels it has.   Most queries to a field want this not of the vertical grid and the existing design requires multiple accesses to info to calculate it.
Surface field  should not have any entry for num levels.  (Using 0 could be made to work, but ...)
"vloc" should be renamed "vstagger"
Parameters for staggering and the strings used for I/O should be colocated.

Long-terming as this seems important.


Freezing embedding layer

I am running KRNM and CKNRM on our own log.
I learned the embeddings on my own dataset (the real documents) with fasttext.
As in your experiences (and other papers), I get a nice boost from CKNRM  compared to KRNM.
However, the result is approximatively the same when the first layer is frozen.
Moreover, the max perf is reached on dev very rapidly (during the first epoch) and then it stays approximatively the same for several epochs (when embedding layer is frozen or not).

Dev in blue, test in red
Because of large bias in our logs, I needed to limit them to 100K queries (and there are 20 docs per SEPR).
Have you noticed the same behaviour on your log datasets? (rapid reach of max + no effect when freezing first layer). Have you tried to add more regularization? (I tried some 50% dropout on embedding layers without real effect)

I have also noticed the instability of Conv-KNRM on my dataset.
I kind of "fixed" it by offsetting the bias in my logs towards first results (using simple click model). Before, perf were very low and unstable, after I always reach high perf.
My feeling is that CNN adds more capacity to capt everything and therefore are very sensible to bias.
Regarding using entity, unfortunately, in my case, I can't use a knowledge base because in my industry there is none which covers our client queries. And reading entity duet paper I was thinking, ok it s just slightly better than CNN but requires a Knowledge base and more computation, so CNN was the obvious choice.

Thank you for your comment. I do not really understand "I kind of "fixed" it by offsetting the bias in my logs towards the first results", and can you describe it more specifically. A short paper in Sigir also demonstrates that training K-NRM more times and incorporate them all can reach better performance. I think you are right and Conv-KNRM amplifies the bias.

Above is a count of click per position on our logs for 1 of our search engine.
Obviously #1st position is much more clicked than second and so on.
The interesting point is that in our case... our search engine just performs boolean search without any traditional relevancy like BM25 or anything else (but few rules to unboost some kind of contents we don't think most of our users are interested into).
My point is that in this specific scenario, I have only position bias. With raw clicks, DL model were performing very poorly (under the position bias). So I removed from our logs the 3 first results and the model performed better. Since then, I found something else which seems intellectually better and make the model perform even better: I only keep search where the user has clicked minimum one time on the second part of the SERP. Because there is no relevancy on our search engine, these queries are specially harder than the other, just the user has looked at the minimum at 50% of the results shown. Not perfect but the model is performing 20 absolute points of MAP better than without doing anything, so I imagine the signal is of better quality after these filters.

In Sogou query log, all the click rates almost have not so much bias. So I think the max-margin loss function can be rewritten in your task, maybe weight each margin ore just use sigmoid function. This idea I have not noticed before, thank you very much! There are lots of works we have to complete.

Hi, for more neural IR training, data augmentation and more about EDRM. Please refer to our WWW2020 Paper Selective Weak Supervision for Neural Information Retrieval. Thank you for your attention. I will close this issue.


Loosen cython reqs

When trying to update napari's packages for archlinux, I got stuck at in-n-out requiring a specific (non-latest) version of cython. As far as I can tell, everything builds fine with a later version (currently testes 3.0.0b3 instead of 3.0.0a11. Can we loosed these requirements here, or should I work around it downstream?

Yeah, it's actually not even using cython (it was experimental).. Will do

have another try with 0.1.8

All good! There's some interesting changes with the name of the package in a few places (pypi download link and tarball mainly), where it was slugified. Maybe a change in pypi?

I switched to hatchling... probably that


Python Tests

Running the example files as part of CI is not sufficient for properly testing our python bindings anymore so we should have a dedicated testing suite for the bindings

Closed by #119


Tag missing

Could you please tag your master branch ?
-> git tag brutespay-1.5
I need these tags to build clean debian packages...
Thank you

tag has been created, closing


Test enhancement

Changed log

Add the white filter list to define the code coverage folder.
Add the php-nightly test in Travis CI build. And let this test can be failed because no one can guarantee this test will always be done.

@peter279k thank you!


Spikes don't hurt you when you get pushed into them

Best example would be when you get moved spikes them by platforms, or getting launched into them by faithplates.

Faithplates work for me, you should post a gif of the behavior. On a platform you don't actually touch the spikes, because you aren't actually moving. There's no simple solution to that

Faithplates work for me, you should post a gif of the behavior. On a platform you don't actually touch the spikes, because you aren't actually moving. There's no simple solution to that

Faithplates work only sometimes, they won't work if you're being launched at an angle i think

Faithplates work as intended to the best of my knowledge, because it does not actually work differently from just walking into them. You should post a video if there is really something wrong


feat: build tank drive train

this is a more complex issue that will take multiple people,
build the drive train to chassis specifications

6 wheel tank drive with a drop center
4 NEO motors, two on each side
Differential drive system


Error: Request failed with status code: 400 Bad Request

Generating commit message from OpenAI...
Error: Request failed with status code: 400 Bad Request
Empty commit message generated. Commit aborted.
my config.toml is below:
openai_api_key = "<MY KEY>"
openai_url = "https://api.openai.com"
openai_model = "GPT-3.5 Turbo"
user_language = "en"

Please try gpt-3.5-turbo

This seems to be an error message returned by the OpenAI service.

according to https://help.openai.com/en/articles/5955604-how-can-i-solve-429-too-many-requests-errors. seems no way to control the request rate.


Android crash when getting message

Install your lib correct and can get device token when run NotificationsAndroid.setRegistrationTokenUpdateListener.
But when getting notification android was crashed (IOS work fine).
Use RN 0.59.9.
build.gradle :
 implementation project(':react-native-firebase')
 implementation "com.google.android.gms:play-services-base:16.1.0"
 implementation "com.google.firebase:firebase-analytics:17.1.0"
 implementation "com.google.firebase:firebase-messaging:20.0.0"

Message from crashlytics:
Fatal Exception: java.lang.RuntimeException: Unable to instantiate service com.dieam.reactnativepushnotification.modules.RNPushNotificationListenerService: java.lang.ClassNotFoundException: Didn't find class "com.dieam.reactnativepushnotification.modules.RNPushNotificationListenerService" on path: DexPathList[[zip file "/data/app/com.umbi-2/base.apk"],nativeLibraryDirectories=[/data/app/com.umbi-2/lib/arm64, /data/app/com.umbi-2/base.apk!/lib/arm64-v8a, /system/lib64, /vendor/lib64]]
   at android.app.ActivityThread.handleCreateService + 3248(ActivityThread.java:3248)
   at android.app.ActivityThread.-wrap5(ActivityThread.java)
   at android.app.ActivityThread$H.handleMessage + 1633(ActivityThread.java:1633)
   at android.os.Handler.dispatchMessage + 102(Handler.java:102)
   at android.os.Looper.loop + 165(Looper.java:165)
   at android.app.ActivityThread.main + 6375(ActivityThread.java:6375)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run + 912(ZygoteInit.java:912)
   at com.android.internal.os.ZygoteInit.main + 802(ZygoteInit.java:802)

It was my mistake, just bad delete previous push library.

Did you use https://github.com/zo0r/react-native-push-notification before? I'm having the same issue and had this library installed before, so I was just wondering what you meant by "bad delete"?


Test manual deployment and usage

See https://github.com/servicecatalog/oscm-approval/blob/master/README.md.

I've made some minor changes to the manual.
Approve, Reject, adding comments works. Information about creating a new approve is sent to e-mail


feat: add @felce

Summary by CodeRabbit

Chores

Updated allowed scopes in package management: removed @scent and added @felce.
No changes made to devDependencies or other core fields in package.json.

https://www.npmjs.com/search?q=%40felce


zppy cannot discover the hostname from a compute node on chrysalis

[ac.ngmahfouz@chr-0493 pipd_cdf6c6e]$ source /lcrc/soft/climate/e3sm-unified/load_latest_e3sm_unified_chrysalis.sh
(e3sm_unified_1.8.0_chrysalis) [ac.ngmahfouz@chr-0493 pipd_cdf6c6e]$ source /lcrc/soft/climate/e3sm-unified/load_latest_e3sm_unified_chrysalis.shD^C
(e3sm_unified_1.8.0_chrysalis) [ac.ngmahfouz@chr-0493 pipd_cdf6c6e]$ zppy -c F2010.PD.NGD_v3atm.9ac9529.chrysalis.cfg
Configuration file validation passed.
Traceback (most recent call last):
  File "/lcrc/soft/climate/e3sm-unified/base/envs/e3sm_unified_1.8.0_chrysalis/bin/zppy", line 10, in <module>
    sys.exit(main())
  File "/lcrc/soft/climate/e3sm-unified/base/envs/e3sm_unified_1.8.0_chrysalis/lib/python3.10/site-packages/zppy/__main__.py", line 84, in main
    machine_info = MachineInfo(machine=machine)
  File "/lcrc/soft/climate/e3sm-unified/base/envs/e3sm_unified_1.8.0_chrysalis/lib/python3.10/site-packages/mache/machine_info.py", line 75, in __init__
    raise ValueError('Unable to discover machine from host name')
ValueError: Unable to discover machine from host name

@mahf708, as discussed in https://github.com/E3SM-Project/mache/issues/58.  This really is a zppy problem.  zppy needs to detect the machine when you're still on a login node and set the machine manually on compute nodes.

I don't think there's any way for mache to handle this so it's a zppy problem if this should work when you launch jobs from a compute node.

@mahf708, if you use the development version of zppy, you should be able to set the machine as a config option and then launch the job on a compute node.  That would be my suggestion.  I don't think @forsyth2 was interested in an automated approach but one other possibility specifically in E3SM-Unified would be to use the $E3SMU_MACHINE variable.

@forsyth2, could you point @mahf708 to an example config file that has the machine config option?

I don't think @forsyth2 was interested in an automated approach

I think the issue was that on some machines it's difficult to tell what machine you're on based on the compute-node name.

@forsyth2, could you point @mahf708 to an example config file that has the machine config option?

I don't seem to have any at the moment, but you can just set machine = to chrysalis. (https://github.com/E3SM-Project/zppy/blob/main/zppy/main.py#L111 shows options for different machines).

a good habit to quickly report quirks

Yes, I agree it's good to document issues and/or feature requests. That said, it's helpful to know if an issue requires immediate attention or not. I just added the "Nice to have" label for this issue. That label tells me I can prioritize other tasks and work on an issue time-permitting (or if enough people request it that it's no longer just "nice to have").

@mahf708, I really think the desired solution to this is that you add:
[default]
machine = chrysalis

(or, obviously, the equivalent for other machines) to your config file if you want to launch a job from a compute node.  We can fix this so it automatically detects the machine in E3SM-Unified for the next release, but that won't help you with the current release or with zppy development environments in the meantime.

I have fixed machine discovery with E3SM-Unified in #511


Fix blocking calls for gRPC even though using Reactor

Description
Make DaprClientGrpc truly async and update unit tests.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #434
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[ ] Extended the documentation

The only thing now is to bring back the hot mono unit tests.

The only thing now is to bring back the hot mono unit tests.


npm "MODULE_NOT_FOUND" error

I'm trying to import Mathlib.Tactic.Ring, and I encounter this error:
`d:\Lean4\lean-4.15.0-rc1-windows\bin\lake.exe setup-file E:/Learn/LEAN/work/Main.lean Init Work Paperproof Mathlib.Data.Rat.Init Mathlib.Tactic.Linarith Mathlib.Tactic.Ring` failed:

stderr:
⚠ [5/690] Replayed BetterParser
warning: .\.\.lake/packages\Paperproof\lean\.\.\BetterParser.lean:41:3: `List.bind` has been deprecated: use `List.flatMap` instead
warning: .\.\.lake/packages\Paperproof\lean\.\.\BetterParser.lean:168:17: `List.join` has been deprecated: use `List.flatten` instead
warning: .\.\.lake/packages\Paperproof\lean\.\.\BetterParser.lean:169:54: `List.bind` has been deprecated: use `List.flatMap` instead
warning: .\.\.lake/packages\Paperproof\lean\.\.\BetterParser.lean:181:26: `List.join` has been deprecated: use `List.flatten` instead
✖ [600/690] Building proofwidgets/widgetJsAll
trace: .\.\.lake/packages\proofwidgets\widget> npm.cmd clean-install
trace: stderr:
node:internal/modules/cjs/loader:1228
  throw err;
  ^

Error: Cannot find module 'e:\Learn\LEAN\work\.lake\packages\proofwidgets\widget\node_modules\npm\bin\npm-prefix.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)
    at Module._load (node:internal/modules/cjs/loader:1051:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v20.18.0
node:internal/modules/cjs/loader:1228
  throw err;
  ^

Error: Cannot find module 'e:\Learn\LEAN\work\.lake\packages\proofwidgets\widget\node_modules\npm\bin\npm-cli.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)
    at Module._load (node:internal/modules/cjs/loader:1051:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v20.18.0
error: external command 'npm.cmd' exited with code 1
Some required builds logged failures:
- proofwidgets/widgetJsAll
error: build failed

I don't know if the problem is with my installation of the mathlib library or with Node.js. I‘d be grateful if someone offer to help!

Hi!  However, if you are just using ProofWidgets4, you shouldn't need Node.js at all: see here. Can you paste your lakefile.toml or lakefile.lean?


How to reproduce  the transferability results?

Hi, How do I reproduce the transferablity table?

Hi, for reproduce the transferability table, you could refer to this folder, which contains the results and the prompts for the transferability experiments.


AI Chatbot for DNCEng Docs: PoC Chatbot Data Ingestion

Create an automatic data pipeline to update the PoC Chatbot with more documentation

Completed the pipeline for the PoC Chatbot. It now has all docs from the Arcade repository.


OData V2 adapter removes the '+' character in next link

Hi colleagues,
we found an issue of OData v2 adapter. It removes the '+' character in next link.
In our cases, we compared adapter v2 with adapter v4 as follows.
OData v4 adapter case:

The request link is like
…/srv/worklistitems/WorklistItems?$format=json&$filter=releaseType_code%20eq%20%27TR+MR%27&&$skip=0&$top=2800&$skiptoken=1000
The returned next link is like
"@odata.nextLink":"WorklistItems?$format=json&$filter=releaseType_code%20eq%20%27TR+MR%27&&$skip=0&$top=2800&$skiptoken=2000"

OData v2 adapter case:

The request link is like
…/srv/v2/worklistitems/WorklistItems?$format=json&$filter=releaseType_code%20eq%20%27TR+MR%27&&$skip=0&$top=2800&$skiptoken=1000
The returned next link is like
"__next":"…/WorklistItems?$format=json&$filter=releaseType_code eq 'TR MR'&$skip=0&$top=2800&$skiptoken=2000"

This affects the working of excel export in UI5. More information will be sent to your team via email.

cds version in our cases:
@cap-js/audit-logging: 0.6.0
@sap/cds: 7.7.3
@sap/cds-bootstrap: 0.5.15
@sap/cds-common-content: 1.2.0
@sap/cds-compiler: 4.7.6
@sap/cds-dk: 7.7.2
@sap/cds-dk (global): 7.0.3
@sap/cds-fiori: 1.2.2
@sap/cds-foss: 4.0.2
@sap/cds-hana: 2.0.0
@sap/cds-indexer: 1.0.14
@sap/cds-lsp: 7.6.1
@sap/cds-migration-check: 1.0.23
@sap/cds-mtxs: 1.16.0
@sap/cds-shim: 0.5.37
@sap/eslint-plugin-cds: 2.6.7
Node.js: v18.20.0

Thanks for reporting this issue. I can produce the issue locally in my test suite. I will have a look... Thx.

First finding is, that + is a special character in URLs. It's used to represent spaces in URLs, as those are not allowed in URLs. That's why + is converted during decode of URL into space again. I need to see, how I can work around that, as OData V4 supports this. Stay tuned.

I also checked OData V4 and there the nextLink calculation for + is wrong as well (New OData Adapter  / New DB Adapter)
Example from my test suite with key WE+DE-SFSNRF:
http://localhost:4004/odata/v4/main/FavoriteLimited?$filter=name eq 'WE+DE-SFSNRF'
Result:
{
<EMAIL_ADDRESS>"$metadata#FavoriteLimited",
<EMAIL_ADDRESS>"FavoriteLimited?%24filter=name%20eq%20'WE%20DE-SFSNRF'&%24skiptoken=1",
  "value": [
    {
      "name": "WE+DE-SFSNRF",
      "value": "+"
    }
  ]
}

The result is correct but the nextLink is wrong as is now contains key WE DE-SFSNR.
So with new OData/DB Adapter this does not work as well anymore with +.
Reason + in URL has special meaning and defacto represents a space...
Correct URL is:
http://localhost:4004/odata/v4/main/FavoriteLimited?$filter=name eq 'WE%2BDE-SFSNRF'
Then the result is also correct:
{
<EMAIL_ADDRESS>"$metadata#FavoriteLimited",
<EMAIL_ADDRESS>"FavoriteLimited?%24filter=name%20eq%20'WE%2BDE-SFSNRF'&%24skiptoken=1",
  "value": [
    {
      "name": "WE+DE-SFSNRF",
      "value": "+"
    }
  ]
}

The issue with OData V2 Adapter is, that the next link is not url component encoded, I will work on that...

Fixed with Commit
https://github.com/cap-js-community/odata-v2-adapter/commits/main/
To be released soon.

Fixed in release:
https://github.com/cap-js-community/odata-v2-adapter/releases/tag/v1.13.5
Always encode + as %2B in URL. Otherwise it's treated as blank character. Please check...


Just be aware that sqlite (sqlite3) does not work with AWS EFS drive.

I got the following error when I tried the command "python vcf2db.py test.vcf test.ped test.db"  at an EFS drive on a cfncluster.  It produced an empty db file.  But it worked if I tried to produce the db file somewhere else, like "python vcf2db.py test.vcf test.ped ~/test.db".

Traceback (most recent call last):
  File "vcf2db.py", line 806, in
    VCFDB(a.VCF, a.db, a.ped, black_list=a.info_exclude, expand=a.expand, blobber=main_blo
bber)
  File "vcf2db.py", line 213, in __init__
    self.samples = self.create_samples()
  File "vcf2db.py", line 534, in create_samples
    t.create()
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/sql/sch
ema.py", line 742, in create
    checkfirst=checkfirst)
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/engine/
base.py", line 1920, in _run_visitor
    conn._run_visitor(visitorcallable, element, **kwargs)
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/engine/
base.py", line 1529, in _run_visitor
    **kwargs).traverse_single(element)
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/sql/vis
itors.py", line 121, in traverse_single
    return meth(obj, **kw)
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/sql/ddl
.py", line 767, in visit_table
    include_foreign_key_constraints=include_foreign_key_constraints
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/engine/
base.py", line 945, in execute
    return meth(self, multiparams, params)
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/sql/ddl
.py", line 68, in _execute_on_connection
    return connection._execute_ddl(self, multiparams, params)
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/engine/
base.py", line 1002, in _execute_ddl
    compiled
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/engine/
base.py", line 1189, in _execute_context
    context)
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/engine/
base.py", line 1393, in _handle_dbapi_exception
    exc_info
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/util/co
mpat.py", line 202, in raise_from_cause
    reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/engine/
base.py", line 1182, in _execute_context
    context)
  File "/home/centos/miniconda/envs/python2/lib/python2.7/site-packages/sqlalchemy/engine/
default.py", line 469, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) disk I/O error [SQL: u'\nCREAT
E TABLE samples (\n\tsample_id INTEGER NOT NULL, \n\tfamily_id VARCHAR(1), \n\tname VARCHA
R(5), \n\tpaternal_id VARCHAR(5), \n\tmaternal_id VARCHAR(5), \n\tsex VARCHAR(2), \n\tphen
otype VARCHAR(2), \n\textra VARCHAR(3), \n\tPRIMARY KEY (sample_id)\n)\n\n']

Thanks for reporting.
closed in #23


Fix imports for {text,image}_dataset_from_directory

Fixes #1180.
Note that I directly modified the generated files since the output should not be affected.

Thanks for choosing the correct squash commit message @fchollet Sorry for the extra commits!


find some issue when installing on CentOS

find some issue when installing on CentOS
1, in CentOS installing, no regist for "package_file"
2, if Master MDM switched, approve_certificate could help  avoid waiting
for 'y' input

Thanks for the contribution


Background tracking even if the user closes the application

Hi, Is there a possibility that the background tracking does not stop even if the user closes the application? But still show the notification.
amazing work!

I have tried to address this here in #19. Merry Christmas!


Integrate check with pipeline

As an AaC developer, I want to ensure that core validations are included within the project pipeline, so that end users can leverage the pipeline to assist with evaluation of their components.
AC:

[ ] Pipeline workflows are modified to incorporate core validators
[ ] Core validators are all properly exercised via the pipeline with passing models
[ ] Core validators are all properly exercised via the pipeline with failing models

[ ] Expansion of allowing passing and failing model for each validator so that a 1:1 relationship is created and maintained

[ ] Expand actions/integration test for returning notice of a pass/fail not being exercised of a validator

Believe the new incorporation of behave in the 0.4.0 work to allow behavioral testing as part of the pipeline accomplishes the integration goal of this task. Need to evaluate and confirm.


Fix NPC not fully loading if constructed when no players are online

Describe the bug
If an NPC is constructed using NPCLib#createNPC() while no players are online, that NPC, no matter when it is created, will only show armor stand lines (not the NPC itself) when calling NPC#show on a certain player. At no point was an exception thrown relating to NPCLib, or during NPC creation, and at no point was the NPCLib instance I was using null.
NPCLib usage option
2
NPCLib JAR name
NPCLib.jar (My JAR is renamed. However, the plugin loader states the plugin name as "NPCLibPlugin v2.11.1-SNAPSHOT").
Server version
git-NachoSpigot-"39f2882" (MC: 1.8.8) (Implementing API version 1.8.8-R0.2-SNAPSHOT)
To Reproduce
Steps to reproduce the behavior:

Used code https://pastebin.com/DweH4itS
Construct & create NPC immediately on server start, or before any players have joined (either one)
Show NPC for any player on join

Expected behavior
I expected for the entire NPC to be spawned, not just its name tags, immediately after a player joined.
Screenshots

Additional context
I actually have already cobbled together a little fix for this problem by queuing an NPC's creation for the next PlayerJoinEvent if no players are currently online. Maybe that'll help?

Im having the same probleme

Same issue over here in 2024 is crazy

@Archonic944 i fixed this bug by spawning an npc for each player on join and only showing it to the player not the best way but its a way and it doesnt cause lags


Migrate rdbms to cloudera.exe & RHEL9 fixes

@clevesque - looks like you need to rebase this PR onto the latest devel branch.


The website requires a while to load the content.

Maybe it is possible to speed this up or by by exporting it all as html and serve that.

it's already statically served with github pages. Content is displayed dynamically with instantsearch.js
it may be slower on mobile than on desktop.

it's already statically served with github pages. Content is displayed dynamically with instantsearch.js
it may be slower on mobile than on desktop.


SEQUENCE_OF_decode_oer and SEQUENCE_OF_encode_oer undeclare here (not in funciton)

Hello lev, I am testing out the OER support for my example asn schema, a very simple schema but i run into problem when i run the make file. The error "SEQUENCE_of_decode_oer" undeclare here. If i use -gen-PEr, then the code works. Only when i used -gen-OER this error pops up. whenever i run the asn1c compiler with the -gen-OER flags, the issue will occur. I think the OER portion might be broken.
I cloned the master newest branch. Does anyone else has similar issue? My Asn schema is pretty simple, in fact is from the Lev's example page.
MyModule DEFINITIONS ::=
BEGIN
MyTypes ::= SEQUENCE {
    myObjectId   OBJECT IDENTIFIER,
    mySeqOf      SEQUENCE OF MyInt,
    myBitString  BIT STRING {
                        muxToken(0),
                        modemToken(1)
                 }
}

MyInt ::= INTEGER (0..65535)
END

Commands
> asn1c -pdu=MyTypes -gen-OER MytestAsn.asn1
> make -f Makefile.am.sample clean
> make -f Makefile.am.sample
>
> Error:
> MyTypes.c:43:2 error: 'SEQUENCE_OF_decode_oer' undeclare here (not in a function)
> SEQUENCE_OF_decode_oer,
>  MyTypes.c:43:2 error: 'SEQUENCE_OF_eecode_oer' undeclare here (not in a function)
> SEQUENCE_OF_eecode_oer,

The compilation failed. but when i change to -gen-PER, it passed. Any idea?
WJL

hi, @wjleong ,
With vlm's newest repository 290b4d6918fe567c412fee2cf139fc82e442ee26, generated code from you sample ASN.1 can be compiled and linked successfully.
The Makefile is modified and re-generated from examples/sample.sample.source.1609.2/Makefile

Hi brchiu,
Thank you! you are right the code can be compile and link. When i am decoding the attached oer file by using command:-
./progname -ioer -oxer data.oer
I get error below:-
Segmentation fault (core dumped)
Appreciate you advice. My whole prupose is to test out the simple oer encoding/decoding so that i can use it on the TCI schema i will be working on...if you have any information about TCI it will be a great help as well!! :)
data.zip

@wjleong, I would suggest you compile your own code with debug information enabled, i.e. with '-g' command line option, then use gdb to find out the place crash.

hello brchiu,
I attached an asn schema and i tried using lev master to compile it and it gives lots of error. Is there a working branch i can use to compile the attached schema? thank you for your help1
WJL
TCIall.zip


Added a blake2 hash function to crypto module

Even though it was overlooked on my part when reviewing the code, but please remember to include the crate in lib.rs


Organize Imports: Make spaces in imports configurable

Organize imports is a welcome feature.
However, it does not match the style that JetBrains Webstorm currently uses. Webstorm auto imports with the style: import {Foo} from "bar"; ... note the lack of spaces in the brackets.
Unfortunately this leads to a lot of churn in git Pull Requests when a team has a mix of Webstorm and VS-Code users.
Suggest making import style configurable, per project via .vscode/settings.json, to include or exclude the spaces in the imports.

Try setting: "javascript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces": false or "typescript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces": false


remove range check and output builtin functionality

Codecov Report

Merging #675 (f3f0874) into main (24c84ab) will decrease coverage by 0.12%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #675      +/-   ##
==========================================
- Coverage   96.78%   96.67%   -0.12%
==========================================
  Files         124      124
  Lines       28876    28695     -181
==========================================
- Hits        27949    27741     -208
- Misses        927      954      +27

Files
Coverage Δ

provers/cairo/src/air.rs
98.52% <100.00%> (-0.14%)
:arrow_down:

provers/cairo/src/execution_trace.rs
98.53% <ø> (-0.94%)
:arrow_down:

provers/cairo/src/runner/run.rs
70.09% <100.00%> (-16.44%)
:arrow_down:

... and 4 files with indirect coverage changes
:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!


Fonts on themes

I really love the Monokai Black theme that you have. Is it possible to have this type of font setting for the theme? With the "class", "def" italics as well?

What you can do is to override the theme in your configuration file, using the custom selectors, and passing them the italic argument. for doing that, i give you links for doing it yourself

https://code.visualstudio.com/docs/getstarted/themes#_customizing-a-color-theme
https://code.visualstudio.com/api/references/theme-color

and for know wich element add to customized your version, you can use the integrated tool in VSCode, by pressing ctrl/cmd + shift + P and select inspect editor tokens ans scopes


nRF52 config

I'd like to try this on a nRF52 dev kit . Are there any special config changes to build for nRF52 ?

I've got it to build for nRF52, it doesn't seem to build fine and merge with SD s132 however it's crashing at some point, haven't got a chance to debug it yet. Please post your progress if you do get it to work.

I mean it does build fine.


Use all_task_data in Replica::expire_tasks

(This will make sense when #372 is finished)
Replica::expire_tasks currently uses Task instead of TaskData, meaning that it is doing extra work to load task dependencies. Refactor it to use just TaskData objects, parsing the "modified" property and comparing it to the expiration time.

Thanks @aricursion!


Fix Coveralls and Add README Badges

Switched coveralls python library
Added coveralls and code-climate badges to README
Changed travis.yml file to cd into miner folder

Coverage now confirmed to work.

Coverage remained the same at 100.0% when pulling 0b9f2971660dad7964ddb82415dd8db788636134 on coveralls into 30c3be199a8b1ce235208384e10d9a1143a65920 on master.

:+1:


Incorrect error message when artifact uploading returns 500

Is your feature request related to a problem? Please describe.
If an artifact upload fails with a 500 response code, an error message is printed showing it will retry 10 times when in fact the code is written to not retry for this error code. So it's a bit confusing to users.

Example error message in job logs:

Responsible code: https://github.com/buildkite/agent/blob/61a06503fe330d93f00415c99d841215d82f8b4f/agent/artifact_batch_creator.go#L75
Describe the solution you'd like
I think this should print an accurate error message that it will not be retrying.
Describe alternatives you've considered
It could also retry as it states 🤷

It's interesting that we're intentionally not retrying on 500. I assume we'll retry on 502/503 from the load balancers though?
The check for 500 was added in ee417c3754ddcd426ac9291e6f728aff4e55ca7d - @keithpitt any idea what 2015 Keith was thinking when making that commit? 😂

Yeah that's my assumption because I fairly sure I've seen it actually retry in the past - although it could be the meta-data command I'm thinking of.
One thought for the reasoning behind this is a thundering heard type issue - if we are having an incident, retrying is just going to get worse.
I also think there are multiple places it could retry - in the initial request to the artifacts API, and then to the pre-signed S3 URL (I think that's how it works anyway)

Confusing! I would have expected it to retry, with an exponential jittered back-off like other things 🤔


fix($parse): do not convert to string computed properties multiple times

Do not convert to string properties multiple times.

Marvellous. LGTM - please merge.

closed with 20cf7d5e3a0af766b1929e24794859c79439351c

@petebacondarwin merged this at master and v1.4.x branch. Do you think this should this be backported to prior versions?

Yes.
On 19 Sep 2015 21:26, "Lucas Mirelmann"<EMAIL_ADDRESS>wrote:

@petebacondarwin https://github.com/petebacondarwin merged this at
master and v1.4.x branch. Do you think this should this be backported to
prior versions?
—
Reply to this email directly or view it on GitHub
https://github.com/angular/angular.js/pull/12892#issuecomment-141703100.

backport to 1.2 with afb65c11e5e3425f8431ad5b82308ff6b8ecbc64
backport to 1.3 with 9d5ac2eb84f21159ff93dac6f3d5782988a5f515

Good work!


drf-spectacular 0.26.4 is causing schema generation to fail

Environment

Nautobot version (Docker tag too if applicable): v1.4.3 and higher
Python version:
Database platform, version:
Middleware(s):

Steps to Reproduce

Update to drf-spectacular 0.26.4
Run nautobot-server spectacular

Expected Behavior
OpenAPI schema generates

Observed Behavior
Traceback:
Traceback (most recent call last):
  File "/opt/nautobot/bin/nautobot-server", line 6, in <module>
    sys.exit(main())
  File "/source/nautobot/core/cli/__init__.py", line 54, in main
    run_app(
  File "/source/nautobot/core/runner/runner.py", line 263, in run_app
    management.execute_from_command_line([runner_name, command] + command_args)
  File "/opt/nautobot/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
    utility.execute()
  File "/opt/nautobot/lib/python3.8/site-packages/django/core/management/__init__.py", line 413, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/nautobot/lib/python3.8/site-packages/django/core/management/base.py", line 354, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/nautobot/lib/python3.8/site-packages/django/core/management/base.py", line 398, in execute
    output = self.handle(*args, **options)
  File "/opt/nautobot/lib/python3.8/site-packages/drf_spectacular/management/commands/spectacular.py", line 72, in handle
    schema = generator.get_schema(request=None, public=True)
  File "/opt/nautobot/lib/python3.8/site-packages/drf_spectacular/generators.py", line 268, in get_schema
    paths=self.parse(request, public),
  File "/opt/nautobot/lib/python3.8/site-packages/drf_spectacular/generators.py", line 239, in parse
    operation = view.schema.get_operation(
  File "/opt/nautobot/lib/python3.8/site-packages/drf_spectacular/utils.py", line 422, in get_operation
    return super().get_operation(path, path_regex, path_prefix, method, registry)
  File "/source/nautobot/core/api/schema.py", line 100, in get_operation
    if "requestBody" not in operation and self.is_bulk_action and self.method == "DELETE":
TypeError: argument of type 'NoneType' is not iterable

This appears to be due to a recent bug fix in drf spectacular https://github.com/tfranzel/drf-spectacular/issues/1025 being incompatible with our overloaded AutoSchema.get_operation method

@gsnider2195 from my testing I think this is something to do with the APIRoot views.


Restart services if handler called

This patch fixes an issue where if hosts have different service lists,
it will prevent restarting changes on services that run later on.
For example, hostA in the mons and rgws group would initiate a config
change and restart of services on all mons and rgws hosts, even though
a separate hostB (which is only in the rgws group) has not had its
configuration changed yet. Additionally, when the second host has its
coniguration changed as part of the ceph-rgw role, it will not initiate
a restart since its inventory name != the first hosts.
To fix this we should run the restart once (which is already the case)
as long as the host is in the appropriate group, and filter to the other
hosts in that group.

@guits - any chance I can get you to take a second look? Appreciate it!

@andymcc sorry for the late response.
I think we better to remove the run_once: true instead.
According to the test I've made, simply using run_once: true has not the expected behavior.
(see results)

Hi @guits so the problem is that the handler gets called on each host if you run it in serial, and then restarts the other hosts?
We could change the group to be ansible_play_hosts in that case - serial would then not run against any hosts but the one in question?
The issue with |last for me, is still that if we have groups that are not unique - e.g. some hosts are in multiple groups, the restart handler does not work as expected. This is because there is a chance that no-change to the conf happened to the "last" host during the service run (because it has already had its conf updated in the previous role) - this in turn means that the restart handler doesnt execute and the other hosts that had their config, updated during the current role, are not restarted.
Perhaps by example I can explain better: If we have hosts: host1, host2, hostLast
host1 and host2 are just rgw hosts, and hostLast is a mon and an rgw:
hostLast will run through during the mon update, its configuration will change and it will run the notification handlers to restart services, and those of other hosts in that group. At this point the configuration for host1 and host2 has not changed.
The rgw role will then run, both host1 and host2 have their configuration changed - hostLast does not (it's already updated). The notification happens for host1 and host2 but because of "|last" and the fact that hostLast has not called the handler the restart never happens, leaving host1 and host2 in a state which does not match the configuration on disk.
We could maybe fix this by setting a var if the config changes (e.g. register: conf_changed) and then doing run_once, but only delegating if the host it is delegating to has "conf_changed = True" set?
IMO the current situation is a bug that needs to be fixed, otherwise we should document that groups need to be uniform and mixing groups is a bad idea.

Actually, we already have play_hosts set which is equivalent to ansible_play_batch:
which is available as a list of hostnames that are in scope for the current ‘batch’ of the play. The batch size is defined by serial, when not set it is equivalent to the whole play.
So we could change this to use "with_items: ansible_play_batch"
instead of groups[mon_names] for e.g.

@andymcc
agree, I think it could be the fix here, do you mind updating your PR ?

Thinking about this a bit more, and looking at the old issue: #1457
I think we can simplify this by checking if the host it will delegate to is in the play_hosts instead of the current host. The handlers have changed such that the "inventory_hostname in play_hosts" is redundant - it has to be in play_hosts to run that task.
Put a new PR in, but it should now:

Only run_once
Delegate to each host in the group, as long as that host is in the play_hosts - which means in serial it will only restart the one host.
Will run as long as one host calls the handler in the current list of play_hosts - which means in serial it will restart each host, but only on that hosts run.

@andymcc It looks good, indeed. I just need to double check something but I think we should be good to merge this.
I know this has been a long time, thanks for your patience!

Of course, no problem - its a pretty core change so I understand the need to take it slow.

@andymcc I took a look at your last patch but I still get some trouble with it :
see here this log is the result of what you propose.
If you look well, you can see daemons are restarted several times.
inventory host file
[mons]
mon0 ansible_host=mon0 ansible_ssh_private_key_file='/Users/guits/.ssh/id_rsa' ansible_ssh_extra_args='-o StrictHostKeyChecking=no'
mon1 ansible_host=mon1 ansible_ssh_private_key_file='/Users/guits/.ssh/id_rsa' ansible_ssh_extra_args='-o StrictHostKeyChecking=no'
mon2 ansible_host=mon2 ansible_ssh_private_key_file='/Users/guits/.ssh/id_rsa' ansible_ssh_extra_args='-o StrictHostKeyChecking=no'

[osds]
mon0 ansible_host=mon0 ansible_ssh_private_key_file='/Users/guits/.ssh/id_rsa' ansible_ssh_extra_args='-o StrictHostKeyChecking=no'
osd0 ansible_host=osd0 ansible_ssh_private_key_file='/Users/guits/.ssh/id_rsa' ansible_ssh_extra_args='-o StrictHostKeyChecking=no

defaults/handlers/main.yml
- name: restart mons
  debug:
    msg: "restarting mons..."
  with_items: "{{ groups['mons'] }}"
  when: item in play_hosts
  delegate_to: "{{ item }}"
  run_once: true
  listen: restart mons

- name: restart osds
  debug:
    msg: "restarting osds..."
  with_items: "{{ groups['osds'] }}"
  when: item in play_hosts
  delegate_to: "{{ item }}"
  run_once: true
  listen: restart osds

With the following code, we can see the handlers are well triggered as supposed :
defaults/handlers/main.yml
- name: restart mons
  debug:
    msg: "restarting mons..."
  with_items: "{{ groups['mons'] }}"
  when: inventory_hostname in groups.get('mons') | last
  delegate_to: "{{ item }}"
  listen: restart mons

- name: restart osds
  debug:
    msg: "restarting osds..."
  with_items: "{{ groups['osds'] }}"
  when: inventory_hostname in groups.get('osds') | last
  delegate_to: "{{ item }}"
  listen: restart osds

which gives this output. Here you can see the behavior is well the expected one.

Hey @guits - I'm trying to think of a good way to change it. I can't think of a way that is as simple as I'd hope, without tracking which hosts have changed (ansible should have a serial restart handler!) - e.g. I only delegate if the host has called the handler. Perhaps that is the only way to implement that properly, otherwise you will get a restart on ALL hosts in the same group, as long as one host in the group has called the handler - which ensures consistency but does wasteful restarts.
To show you the current issue though, if you were to change the inventory such that mon2 was an osd host and mon0 was not, and then change osd0 to be called aosd0 (forcing it to not be the |last host) - you'll see different results for the second run - which is essentially the problem.

I think we can streamline my current PR more by removing "item in play_hosts", since it will now only run if the host has the fact set, which means it already has to be in play_hosts. will fix that quickly

@andymcc
That current patch is now ready to be merged.
Thanks for your patience and the time spent on this.

Thanks @andymcc!


CI - update GitHub actions to node20

CI - update GitHub actions to node20
Address deprecation warnings in CI workflow annotations at
https://github.com/quantumlib/unitary/actions/runs/11221964643
Namely update to

actions/checkout@v4 per https://github.com/actions/checkout/blob/main/CHANGELOG.md
actions/setup-python@v5 per https://github.com/actions/setup-python/releases/tag/v5.0.0

@dstrain115 - PTAL

BTW, I think you need to merge this on your side, I don't seem to have a write access for this repo.


Replace docker-compose with docker compose

Looks like docker-compose v1 has been removed from GitHub Actions. The newer command docker compose should be used instead.
All compose files here seem to use v2 or v3 manifests so this should be a simple command replacement.
https://github.com/actions/runner-images/issues/9557

Build failures appear to be unrelated ot this change. I'm going to merge so I can start trying to fix the individual builds.


1.3.1 reactive-context override reactive-scope

$scope.getReactively and $scope.helpers are defined by reactive-context causing unexpected results only after 1.3.1

The goal is to make both $scope.getReactively and this.getReactively work.
Can you please share what is that a problem you are experiencing?

I reuse your example but with $scope
myModule.controller('MyCtrl', ['$scope', function($scope) {
  $scope.myUser: {
    id: 10
  };

  $scope.helpers({
    myData: () => {
      return Data.find({_id: $scope.getReactively('myUser.id')});
    }
  });

  $scope.myUser.id = 29;
}]);

Problem: $scope.getReactively('myUser.id') return undefined.
I find that $scope.getReactively is pointing to the method defined in reactive-context and not in reactive-scope.

By the way, I have no issue with the this version

Ohhh, you need to change
$scope.myUser: {
    id: 10
};

to
$scope.myUser = {
    id: 10
};

Where is the example so I can update it as well?

Well unfortunately no...
Here a little repo that show what looks like an issue, it's the same example but the result is 10 and not 29.
https://github.com/hlehmann/angular-meteor-demo/blob/master/client/hello.js#L10

After a timeout it seems to work
angular.module('app').controller('MyCtrl', ['$scope', '$timeout', function ($scope, $timeout) {
    $scope.myUser = {
        id: 10
    };

    $scope.helpers({
        myData() {
            return $scope.getReactively('myUser.id');
        }
    });
    console.log(1, $scope.myData);

    $scope.myUser.id = 29;
    console.log(2, $scope.myData);

    $timeout(()=> {
        $scope.myUser.id = 53;
        console.log(3, $scope.myData);
    }, 100);

    $timeout(()=> {
        console.log(4, $scope.myData);
    }, 200);
}]);

console:
1 10 hello.js:13:5
2 10 hello.js:16:5
3 10 hello.js:20:9
4 53 hello.js:24:9

@hlehmann , fixed in https://github.com/Urigo/angular-meteor/commit/d42a1853807c1604b4391f030115bf9ab7679ee6
@netanelgilad @Urigo, please review it

@Urigo What does this mean:
[angular-meteor][helpers] Your tried to create helper for primitive 'searchText', please note that this feature will be deprecated in 1.4 in favor of using 'getReactively' - http://www.angular-meteor.com/api/1.3.1/get-reactively
Do we need to use again:
this.getReactively('searchText')
instead of defining in helpers?


Backport 2.16: Add DER encoded test CRTs to library/certs.c

This is the backport of #2260 to Mbed TLS 2.16.

I re-created the backport on the basis of the updated #2254, backporting also https://github.com/ARMmbed/mbedtls/commit/462c3e5210aa89d931341576541bd58f9ef7bba0 to resolve merge conflicts.

@k-stachowiak Could you please re-review?

@AndrzejKurek Could you please re-review this, too?

Shouldn't we resolve the changelog conflict to let CI pass (now with the new after-merge tests)?

@AndrzejKurek @k-stachowiak Could you please re-review the recent rebase?

@AndrzejKurek @k-stachowiak Could you please re-review?

@AndrzejKurek @k-stachowiak I updated the backport to reflect the current state of #2260 - could you please re-review?


Issue #57 Remove pull secret from k8s secret resource

We have pull secret part of etcd db which is replaced by an empty
json string {} and also remove it from the VM disk side.

OK to merge or wait for the CRC side?


Passport 8.x compatibility

The current version is compatible up to 7.x. Installing this dependency on a setup with passport 8.x will yield errors.

@MattApril do you want to make pull request?

Yes, I can find some time today hopefully. I did not think this was still
maintained.
On Tue, Apr 20, 2021, 7:42 AM Robert Kummer @.***>
wrote:

@MattApril https://github.com/MattApril do you want to make pull
request?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ipunkt/laravel-oauth-introspection/issues/12#issuecomment-823205653,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCK5MPAPVH4HJH3ARDAELDTJVSA3ANCNFSM4KHA5NSA
.

I suppose Passport 10.x compatibility also yields errors, of course.

It seems to be working with some modifications found in this fork:
https://github.com/userh-dev/laravel-oauth-introspection


azure-mgmt-iotcentral needs docstring updates for sphinx

ACTION NEEDED: All sphinx errors and warnings must be fixed by 2024-04-15. The build will begin to fail for this library if errors are not fixed.
This issue indicates that your library reference documentation is rendering with errors. To avoid customer issues, please ensure you take care of these errors and warnings ASAP.
Library name: azure-mgmt-iotcentral
Sphinx build: Link to build (2024-06-01)
How to fix: Run the strict-sphinx tox command at the library package-level and resolve the docstring errors and warnings.

../azure-mgmt-iotcentral>pip install "tox<5"

../azure-mgmt-iotcentral>tox run -e strict-sphinx -c ../../../eng/tox/tox.ini --root .

Once resolved, set strict_sphinx = true in the package's pyproject.toml file.

See Sphinx and docstring checker for more information.

Failed due to a transient error in the pipeline: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3838026&view=logs&j=e5b925a9-9650-5321-24fd-5d9499fe02b8&t=0d206e13-b346-5d3f-79e6-d5bfba9e089e&l=414
No actual sphinx errors so closing.


FR: Passing options

PHPUnit allows you to pass options.
As you've probably seen in the Test-Driven Laravel course already, there's a section on integration testing that explains why you may want to run the whole suite excluding certain groups.
It would be awesome to be able to configure additional options for each of the three test types (method, class, and suite).

Makes sense! How were you thinking of this being implemented? Text fields in the package settings for each command?

I was wondering about that, too… At first, I was thinking it'd be nice to have inputs dedicated to each setting, but that'd probably just be a waste of time for whomever writes that code and overwhelming for users.
Text fields are probably the most flexible and simplest solution.

I'm particularly interested in seeing progress on this as I want to be able to run Laravel Dusk tests. The tests do run at present, however because you aren't able to pass additional commands, the .env.dusk.* file isn't renamed prior to the test running, which results in various testing errors.


#318 InterpreterPlaceholder instances are making it into saved options

Adds a default InterpreterConfiguration for placeholders to ensure they can be displayed in the UI correctly.

:+1:


php7

i have good experience with how you setup the basic apache-php together
can you update this to php7? would be wonderful

Tutum has shut down as of May 31st 2016 (they were acquired by Docker), so I don't think their images will be getting updated at all.
I've created a php7 version here: https://github.com/OscarBarrett/apache-php7
obarrett/apache-php7 on Docker Hub.

i already created my own php7 fpm nginx image, closing this as it is no longer needed, thanks


[5.5] [CS] Don't bail out of CollectVarRefs early

5.5 cherry-pick of https://github.com/apple/swift/pull/38542

Upon encountering an ErrorExpr, we were previously bailing from the walk. However, for multi-statement closures, that could result in us missing some variable references required to connect to the closure to its enclosing context. Make sure to continue walking to catch those cases.
SR-14709
rdar://78781677

@swift-ci please test


Updating the mediaflux version so tests will pass

fixes #1006

coverage: 84.655%. remained the same
when pulling 8c2fa05e03088aa53ccac25f8c1c6be2c9dbe930 on fix-mediaflux-version
into 555f88f1faf689e1d3784ef07c761f71dd98c4cb on main.


Feeding Forum Cell Components with Live Data

Feeding in Discourse API data into the Forum Cells, specifically the top 5 latest posts.

Note for Future Work:

Currently, this component doesn't 'poll' every interval like originally planned. Instead, it fetches live data with every refresh. I ran into some errors for polling, and will be resolving them in the future.
We could improve the UI (like adding headers in the FLIPs cell and colouring)

Nice!


small inconsistency (easy fix)

Docs say : @include clearfix;
Mixin (_utilities.scss, line 36) :  @mixin clear-fix()
(Slight preference towards "clearfix" as for naming)

Corrected documentation. Didn't change the code to avoid breaking existing user code.


Show more/all trades

@jorisbontje:

amans on slack requested the feature to show more trades from the history than just the last 10;
I can see two options for this:

we add a "Show more/all trades" link which removes the limit to the filter
we add an "export to CSV" and allow the user to download the raw data; not sure if this is possible  > to do client side.

(ported from  Show more/all trades #125

@pimato:

in Poloniex they have both options and I use both of them. This implementation would be perfect!

Update this with the current master branch.
Is this superseded by #22 since this only adds "more orders" to last trades?


Setting Page Title (2)

The previous thread hasn't got any solition but was closed:
https://github.com/ReactTraining/react-router/issues/2844
This is a follow-up with the same name.
So the goal is to change titles when routes are changed. IIUIC we need to configure a middleware properly to get it working, but in the previous topic nobody posted an example of this. Please provide one.

You're looking for react-helmet

It is pretty sad to introduce a new dependency for something that is a one-line change.
In the History object, there is a push function that is a wrapper for the DOM object pushState: https://developer.mozilla.org/en-US/docs/Web/API/History_API
However, this wrapper function takes out the "title" option and sets it to null.
  function push(path, state) {
    process.env.NODE_ENV !== "production" ? warning(!(typeof path === 'object' && path.state !== undefined && state !== undefined), 'You should avoid providing a 2nd state argument to push when the 1st ' + 'argument is a location-like object that already has state; it is ignored') : void 0;
    var action = 'PUSH';
    var location = createLocation(path, state, createKey(), history.location);
    transitionManager.confirmTransitionTo(location, action, getUserConfirmation, function (ok) {
      if (!ok) return;
      var href = createHref(location);
      var key = location.key,
          state = location.state;

      if (canUseHistory) {
        globalHistory.pushState({
          key: key,
          state: state
        }, null, href);

        if (forceRefresh) {
          window.location.href = href;
        } else {
          var prevIndex = allKeys.indexOf(history.location.key);
          var nextKeys = allKeys.slice(0, prevIndex === -1 ? 0 : prevIndex + 1);
          nextKeys.push(location.key);
          allKeys = nextKeys;
          setState({
            action: action,
            location: location
          });
        }
      } else {
        process.env.NODE_ENV !== "production" ? warning(state === undefined, 'Browser history cannot push state in browsers that do not support HTML5 history') : void 0;
        window.location.href = href;
      }
    });
  }

This change can literally be done by just respecting the underlying browser API.

function push(path, state, title) {
process.env.NODE_ENV !== "production" ? warning(!(typeof path === 'object' && path.state !== undefined && state !== undefined), 'You should avoid providing a 2nd state argument to push when the 1st ' + 'argument is a location-like object that already has state; it is ignored') : void 0;
var action = 'PUSH';
var location = createLocation(path, state, createKey(), history.location);
transitionManager.confirmTransitionTo(location, action, getUserConfirmation, function (ok) {
if (!ok) return;
var href = createHref(location);
var key = location.key,
state = location.state;
  if (canUseHistory) {
    globalHistory.pushState({
      key: key,
      state: state
    }, title, href);

    if (forceRefresh) {
      window.location.href = href;
    } else {
      var prevIndex = allKeys.indexOf(history.location.key);
      var nextKeys = allKeys.slice(0, prevIndex === -1 ? 0 : prevIndex + 1);
      nextKeys.push(location.key);
      allKeys = nextKeys;
      setState({
        action: action,
        location: location
      });
    }
  } else {
    process.env.NODE_ENV !== "production" ? warning(state === undefined, 'Browser history cannot push state in browsers that do not support HTML5 history') : void 0;
    window.location.href = href;
  }
});

}

@OnkelTem Your best bet is to just put
document.title = 'some title' in your componentDidMount() method on the component being rendered by a route and hope that nothing blows up your component while its loading.

I've created the following solution. Because this is a really useful feature a lot of guys are asking for I've wrote a documentation and published it on npm and github. Would be nice to get some feedback also if it's working in your environment because I don't have test environments for all cases yet as well as automated test (PRs welcome).
https://github.com/lynoapp/react-router-title


Move from pylint to ruff?

Ruff is much faster, and has broad support.
https://github.com/akx/pylint-to-ruff could help.
https://github.com/astral-sh/ruff/issues/970#issuecomment-1677732895 could also help.

A note from my team, we switched from flake8 to ruff ~6 months ago. We still use pylint because it still enough stuff that ruff fails to find. Maybe in 1-2 years ruff will also make pylint obsolete. We run the linters using https://pre-commit.com/ as this makes it very easy to maintain.

I'm slowly working on this.


Fail to build examples/mnist-inference-web

Describe the bug
When building wasm to follow https://github.com/tracel-ai/burn/tree/main/examples/mnist-inference-web, it fails to build it  as follows.
$ ./build-for-web.sh wgpu
error: lto cannot be used for `proc-macro` crate type without `-Zdylib-lto`
error: could not compile `zerocopy-derive` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `walrus-macro` (lib) due to 1 previous error
error: could not compile `serde_derive` (lib) due to 1 previous error
error: failed to compile `wasm-bindgen-cli v0.2.92`, intermediate artifacts can be found at `/var/folders/sp/srxtqmsj43q17d8vhfjsbrdm0000gn/T/cargo-installeGnqzX`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
Error: Installing wasm-bindgen with cargo
Caused by: Installing wasm-bindgen with cargo
Caused by: failed to execute `cargo install`: exited with exit status: 101
  full command: "cargo" "install" "--force" "wasm-bindgen-cli" "--root" "/Users/Library/Caches/.wasm-pack/.wasm-bindgen-cargo-install-0.2.92" "--version" "0.2.92"

To Reproduce
$ ./build-for-web.sh wgpu

When targeting ndarray, the result is the same, causes the same error.
Expected behavior
Successfully built.
Desktop (please complete the following information):

OS: macOS 14.4.1

Additional context
To resolve this issue, I propose removing the -C lto=fat option from RUSTFLAGS. This change will ensure compatibility with proc-macro crates and prevent the build errors.
The link in the rust   indicates lto cannot be used for proc-macro crate type without -Zdylib-lto, and -Zdylib-lto is not included in the standard rustc, the way I see it.

Merged, so close this issue.


caprine: init at 2.60.1

Description of changes
This package is built with buildNpmPackage and electron instead of using binaries. I can only test it in x86_64 so I wonder if anyone can help me test others?
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 332468 run on aarch64-darwin 1

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4417


Cursor resets to top of file when telescope closes

The cursor is set to the top of the file when the recent files telescope window is closed. The cursor should not move from it's original position.

This plugin does not do anything that could cause such behavior. Perhaps this is caused by some other plugin that you have?

Closing due to no reply or repro.