Add a Gitter chat badge to README.md

eBay/parallec now has a Chat Room on Gitter
@jeffpeiyt has just created a chat room. You can visit it here: https://gitter.im/eBay/parallec.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Current coverage is 91.96%

Merging #1 into master will increase coverage by +0.29% as of 030c018

@@            master      #1   diff @@
======================================
  Files           80      80
  Stmts         3088    3088
  Branches       287     287
  Methods          0       0
======================================
+ Hit           2831    2840     +9
+ Partial        113     109     -4
+ Missed         144     139     -5

Review entire Coverage Diff as of 030c018

Powered by Codecov. Updated on successful CI builds.


RFC: SystemParam::user_meta

Objective
The objective of this RFC is the same as in https://github.com/bevyengine/bevy/pull/10618: how to declare one system depends on the other while keeping such configuration robust to the changes.
Solution
Previous RFC suggested making it native to Bevy: each system param could declare before/after system sets.
Some considered that RFC too controversial and not fitting well into Bevy ESC model.
API: user metadata
This RFC proposes alternative solution to the problem. Each SystemParam can supply arbitrary metadata. Metadata is a Rust value of arbitrary type.
trait SystemParam {
  // Implemented by a user.
  fn user_meta(request: &mut SystemParamUserMetaRequest);
}

// This type cannot be instantiated by a user (no need).
impl SystemParamUserMetaRequest {
  // Collect the value of type `T` if requested, ignore otherwise
  fn provide_value<T>(&mut self, value: T) { ... }
}

impl dyn System {
  // User facing API to fetch metadata.
  fn param_user_meta_dyn<T>(&self) -> Vec<T> {
    // Initialize SystemParamUserMetaRequest
    // collect meta from all the params
  }
}

API is similar to Error::provide API from rust stdlib.
How it can be used
A user outside of Bevy can declare two special parameter types: Before<T: SystemSet> and After<T: SystemSet>. These parameter types would emit metadata like BeforeItem(InternedSystemSet) and AfterItem(InternedSystemSet).
Bevy would not automatically do anything with this knowledge (it is just opaque metadata for the scheduler).
But a user can implement utilities over App to account for this metadata to adjust the scheduler.
In pseudocode:
fn my_add_system(app: &mut App, schedule: ScheduleLabel, system: IntoSystem) {
  let system = system.into_system();
  let before = system.param_user_meta_dyn::<BeforeItem>();
  let after = system.param_user_meta_dyn::<AfterItem>();
  let mut system = system.into_system_configs();
  for before in before {
    system = system.before(before);
  }
  for after in after {
    system = system.after(after);
  }
  app.add_systems(schedule, system)
}

Meta vs builtin
Frankly I don't see any applications of param meta outside of these scheduling labels, and this meta will not be very ergonomic (although it would solve the problems I described in the previous RFC). So I would prefer scheduling instructions to be built in Bevy.
But I'd be fine with any solution which would solve the problem, even if user code would be verbose.
 If this idea is not good enough either, I think I can live with existing API which requires looking very hard to verify schedule correctness.

I like that this is less intrusive.
The notion of being able to add arbitrary user-defined meta-data is an interesting hook for extension. And plumbing it up from system params makes sense.
I'm unsure if this would be useful for anything else, but perhaps others will have ideas.
In the absence of that, I don't think this is a good use of developer effort or internal complexity.


Advanced filters

Coverage decreased (-31.9%) to 65.915% when pulling ba0db76c7dc601ba5e583f7d1d378c57e3129edf on advanced-filters into 8ac56b7fd605721f8bed41b7f4fcf3c711002afc on master.


add dark mode to banner

Add dark mode to banner (Though it might not need it).

This didn't turn out to be necessary. The banner itself has a dark gradient over it, and the text stays solid white in order to contrast with the background image. A lighter shade of white loses some of that contrast, which isn't good given the background.


Impersonation email Notification

Public Issue: https://github.com/wso2/product-is/issues/20066
Purpose
When the impersonator acquired impersonated token, we need to send an email to end user about the impersonation based on tenant configuration.

[x] OAuth PR merged

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/9476006976

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/9476006976
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/9476095665

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/9476095665
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/9476294435

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/9476294435
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/9476460783

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/9476460783
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/9476569338

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/9476569338
Status: success


Add watch to npm scripts

@DanielRosenwasser could you review this PR?

Looks good to me - if you want to revert it to colons in another PR, you've convinced me to the point of neutrality on the matter 😄

@DanielRosenwasser Done. :)


add dns_logs to logpush schema validation

The dataset dns_logs is supported by the Logpush service but not included in the schema validation for the cloudflare_logpush_job resource.
I have used this locally and all looks to be working as expected.

looks good; let's get the documentation updated (https://github.com/cloudflare/terraform-provider-cloudflare/blob/master/website/docs/r/logpush_job.html.markdown) and this is good to merge.

thank you @trjstewart 🤙


Uses github workflow instead of Travis

i took the  Github Actions-related commit out of #30, so that @JKatzwinkel has a base if he wanted to add further eXist versions to be tested agaianst.

ha, i'm allowed to merge here too. i had forgotten.

i'm so sorry to have woken up the machines.

well they do seem to be quite ruhe gebend am sein now..


Feature: add version badges

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[x] This PR adds tests for the most critical parts of the new functionality or fixes.

What
Add cosmetic badges to the repo readme, to convey more information to the users about the latest version available.
Why
Close #545.

Reference Server Preview is available here:https://anchor-ref-pr587.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr587.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr587.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr587.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr587.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr587.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr587.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr587.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr587.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr587.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr587.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr587.previews.kube001.services.stellar-ops.com/


Fix packfile subject code bug

Fixes #557
Review Checklist

Tests were added to cover all code changes
Documentation was added / updated
Code and tests follow standards in CONTRIBUTING.md

We might get a sad coveralls output since the database.py call structure is tested but not the individual update scripts.


Windows-2022 Agent with WDK does not provision WDK platform toolsets in Visual Studio 2022

Description
We have successfully run printer driver creation pipelines with Windows-2019 agent and Visual Studio 2019.  The pipelines build projects that reference WDK platform toolsets such as WindowsUserModeDriver10.0.
Now migrated to local Visual Studio 2022 and updated WDK. WDK platforms are available, and builds are successful locally.
But, build pipeline run on agent Windows-2022 fails. Error:
"The build tools for WindowsUserModeDriver10.0 (Platform Toolset = 'WindowsUserModeDriver10.0') cannot be found."
I note that WDK docs say WDK Visual Studio extentions might need a separate VSIXinstaller step to install, but that was not the case in our local Visual Studio 2022 and WDK install.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions

Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
Build started 7/25/2022 4:19:33 PM.
Project "D:\a\1\s\Package\Package.vcxproj" on node 1 (Clean target(s)).
CoreClean:
Creating directory "Release\int".
Project "D:\a\1\s\Package\Package.vcxproj" (1) is building "D:\a\1\s\InfFile\InfFile.vcxproj" (2) on node 1 (Clean target(s)).
CoreClean:
Creating directory "int".
Done Building Project "D:\a\1\s\InfFile\InfFile.vcxproj" (Clean target(s)).
Done Building Project "D:\a\1\s\Package\Package.vcxproj" (Clean target(s)).
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:01.63
"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\msbuild.exe" "D:\a\1\s\Package\Package.vcxproj" /nologo /nr:false /dl:CentralLogger,"D:\a_tasks\MSBuild_c6c4c611-aa2e-4a33-b606-5eaba2196824\1.199.0\ps_modules\MSBuildHelpers\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll";"RootDetailId=|SolutionDir=D:\a\1\s\Package|enableOrphanedProjectsLogs=true"*ForwardingLogger,"D:\a_tasks\MSBuild_c6c4c611-aa2e-4a33-b606-5eaba2196824\1.199.0\ps_modules\MSBuildHelpers\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll"  /p:platform="x64" /p:configuration="Release" /p:_MSDeployUserAgent="VSTS_7372a1f7-1b06-424a-9843-4054c7515a72_build_131_0"
Build started 7/25/2022 4:19:35 PM.
##[error]C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(440,5): Error MSB8020: The build tools for WindowsUserModeDriver10.0 (Platform Toolset = 'WindowsUserModeDriver10.0') cannot be found. To build using the WindowsUserModeDriver10.0 build tools, please install WindowsUserModeDriver10.0 build tools.  Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
Project "D:\a\1\s\Package\Package.vcxproj" on node 1 (default targets).
Project "D:\a\1\s\Package\Package.vcxproj" (1) is building "D:\a\1\s\InfFile\InfFile.vcxproj" (2) on node 1 (default targets).
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(440,5): error MSB8020: The build tools for WindowsUserModeDriver10.0 (Platform Toolset = 'WindowsUserModeDriver10.0') cannot be found. To build using the WindowsUserModeDriver10.0 build tools, please install WindowsUserModeDriver10.0 build tools.  Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". [D:\a\1\s\InfFile\InfFile.vcxproj]
Done Building Project "D:\a\1\s\InfFile\InfFile.vcxproj" (default targets) -- FAILED.
Done Building Project "D:\a\1\s\Package\Package.vcxproj" (default targets) -- FAILED.
Build FAILED.
"D:\a\1\s\Package\Package.vcxproj" (default target) (1) ->
"D:\a\1\s\InfFile\InfFile.vcxproj" (default target) (2) ->
(PrepareForBuild target) ->
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppBuild.targets(440,5): error MSB8020: The build tools for WindowsUserModeDriver10.0 (Platform Toolset = 'WindowsUserModeDriver10.0') cannot be found. To build using the WindowsUserModeDriver10.0 build tools, please install WindowsUserModeDriver10.0 build tools.  Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". [D:\a\1\s\InfFile\InfFile.vcxproj]
0 Warning(s)
1 Error(s)

Time Elapsed 00:00:00.27
##[error]Process 'msbuild.exe' exited with code '1'.
Finishing: Build KipV4Win Package (includes InfFile project build)
Is it regression?
sort of. Was OK using pipeline agent Window-2019
Expected behavior
On agent Windows-2022 the Visual Studio WDK extensions should be installed and available to the pipeline.
Actual behavior
Using agent Windows-2022, WDK extensions for Visual Studio 2022 do not seem to be installed. We get error:
"The build tools for WindowsUserModeDriver10.0 (Platform Toolset = 'WindowsUserModeDriver10.0') cannot be found."
Repro steps
Run pipeline on Agent-2022 that runs Visual studio project that uses Platform toolset WindowsUserModeDriver10.0.

I have found this may be same issue as #5897, and will try the fix reported there.

I tried to install WDK.vsix by running Powershell task with inline script as suggested in #5897 :
$FilePath = Resolve-Path "C:\Program Files (x86)\Windows Kits\10\Vsix\VS2022*\WDK.vsix:
Install-VsixExtension -FilePath $FilePath -Name "WDK.vsix" -VSversion "2022" -InstallOnly
Task seems to start OK, but after 10 minutes with no visible progress, I cancelled. How long should this take? Any suggestions for troubleshooting?  Here is task output, up to point where  I cancelled.
Starting: Add WDK extensions to Visual Studio 2022
Task         : PowerShell
Description  : Run a PowerShell script on Linux, macOS, or Windows
Version      : 2.200.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
Generating script.
========================== Starting Command Output ===========================
"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a_temp\c1a7f8f8-9e36-40ef-922f-f39e68b3fa87.ps1'"
Starting Install WDK.vsix...
Thanks for your suggestions.
-Paul

@plimburg,  it takes 10-30 minutes.

@al-cheb,
Yikes, too long for iterative development.
Looks like I'll have to purge the WDK extensions from my projects, and just use their tools separately.
Thanks for the quick response.


Doesn't work with Rider 2021.1.3

I installed the plugin vie the JB website and it just themes the outer window but not the code area.

Thank you for your interest
I use the plugin every day. The version of Rider I'm using is 2021.3.1, everything works.
Let's look for what the problem is, could you please send a screenshot

This is how it looks for me, I tried installing it via the plugins manager in Rider but it's the same result.

You need to select a plugin in both sections

That was it 👯 nice thank you very much!!! Maybe worth an addition in the docs ;)

Now I will definitely add, thank you very much! :)


App data framework

This pull request is only for review do not merge
Known issues left to fix:
Add support for metadata in aggregations
There is a bug in dimensions computation producing incorrect aggregations.

Also need to add websocket output to pi and twitter demos

Just FYI, we will need to identify the files that belong to Malhar and those to Megh and will need to create a squashed commit for each.

Tim, please make the websocket changes a separate request.
--
sent from mobile
On Jun 25, 2015 4:46 PM, "ilooner"<EMAIL_ADDRESS>wrote:

Also need to add websocket output to pi and twitter demos
—
Reply to this email directly or view it on GitHub
https://github.com/DataTorrent/Malhar/pull/1450#issuecomment-115431997.

And squash please.
--
sent from mobile
On Jun 25, 2015 6:29 PM, "David Yan"<EMAIL_ADDRESS>wrote:

Just FYI, we will need to identify the files that belong to Malhar and
those to Megh and will need to create a squashed commit for each.
—
Reply to this email directly or view it on GitHub
https://github.com/DataTorrent/Malhar/pull/1450#issuecomment-115452592.


chore(deps): Unpin sqlparse dependency

SUMMARY
The blocking issue has been fixed upstream. Bump sqlparse to version 0.4.3. Change suggested in discussion https://github.com/apache/superset/discussions/21580

You're welcome :-)

Thanks @ecederstrand. I was just about to make this change after realizing that the blocking issue had been fixed as our current version wasn't removing backticks per the sqlparse.utils.remove_quotes method.


Add local IJ filters

This PR adds a new filter application, and adds a new option to kRing filter (to cover the kRingDistances function).
We should begin thinking about how to better handle command line arguments and help texts. We might want to consider either adding our own simple options library or depending on another one.
There's also a small code cleanup to not hard code the polar pentagon base cell identifiers.

Coverage remained the same at 100.0% when pulling 2c387cbb58f28cf5fb5cc8d9e0369cab0913ee52 on isaacbrodsky:ij-filters into 8b931671b76a4d89a44272452552325e666213ee on uber:master.


Cannot create table from metadata file

[2024/06/05 16:11:18.690 +08:00] [ERROR] [] ["DB::Exception: Cannot create table from metadata file /data/deploy/install/data/tiflash-9000/metadata/db_1077654/t_1487435.sql, error: DB::Exception: Cannot parse string 'CURRENT_DATE' as MyDate: syntax error at position 8 (parsed just 'CURRENT_'), stack trace:\n\n       0x1c54f3e\tDB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&, int) [tiflash+29708094]
/data/deploy/install/data/tiflash-9000/metadata/db_1077654/t_1487435.sql:
ATTACH TABLE t_1487435
(
id Int32,
company Nullable(String),
illegal_person Nullable(String),
original_qualifications_levels Nullable(String),
now_qualifications_levels Nullable(String),
registered_capital Nullable(String),
dataid Nullable(String),
declaration_type Nullable(String),
declaration_time Nullable(String),
annex_path Nullable(String),
annex_web_url Nullable(String),
dataid_new Nullable(String), q
data_caiji Nullable(MyDate) DEFAULT CAST('CURRENT_DATE' AS Nullable(MyDate)),
apt_code Nullable(String),
apt_code_date Nullable(MyDate),
project_name Nullable(String),
project_id Nullable(String),
company_id Nullable(String),
company_name Nullable(String),
apt_name Nullable(String)
)
ENGINE = DeltaMerge(id,

Hi @z070204z ,
Can you post the CREATE TABLE statement of the table with table_id=1487435 to this issue?
You can find out the table_schema and table_name by executing following statement on tidb.
select table_schema,table_name,'' as partition_name,tidb_table_id from information_schema.`tables`
where tidb_table_id = 1487435
union
select table_schema,table_name,partition_name,tidb_partition_id from information_schema.`partitions`
where tidb_partition_id = 1487435


tsc can't compile examples

When running the node examples with ts-node, all is good, but if I want to compile with tsc I'm getting the following error:
tsc faceDetection.ts
../../node_modules/@types/webgl2/index.d.ts:582:13 - error TS2403: Subsequent variable declarations must have the same type.  Variable 'WebGL2RenderingContext' must be of type '{ new (): WebGL2RenderingContext; prototype: WebGL2RenderingContext; readonly ACTIVE_ATTRIBUTES: number; readonly ACTIVE_TEXTURE: number; ... 556 more ...; readonly WAIT_FAILED: number; }', but here has type '{ new (): WebGL2RenderingContext; prototype: WebGL2RenderingContext; readonly ACTIVE_ATTRIBUTES: number; readonly ACTIVE_TEXTURE: number; ... 557 more ...; readonly MAX_CLIENT_WAIT_TIMEOUT_WEBGL: number; }'.

582 declare var WebGL2RenderingContext: {
                ~~~~~~~~~~~~~~~~~~~~~~

  ../../../../../../../../usr/local/lib/node_modules/typescript/lib/lib.dom.d.ts:16316:13
    16316 declare var WebGL2RenderingContext: {
                      ~~~~~~~~~~~~~~~~~~~~~~
    'WebGL2RenderingContext' was also declared here.

Found 1 error.

So WebGL2RenderingContext is being declared in two separate parts...
Thanks

Hi @asystat  Did you find any solution?
we are getting same error

for those who come here in the future:
https://github.com/tensorflow/tfjs/issues/2007


Internalize _CharacterClassModel

Rip out unused _CharacterClassModel API and make it an internal type by removing the last use of makeDSLTreeCharacterClass.

@swift-ci please test


Fixed tons of 404 due to bug in file template

it's wrong to load balance here, file is married with particular node on upload, so we can't choose node for downloading.
Sorry for no test,  your tests seem to be required a full refactoring =\

@apocarteres Thanks! 😊


Use ET timezone for vpn cohort

Task/Issue URL: https://app.asana.com/0/488551667048375/1206034019967211/f
Description
Use ET tz for vpn cohort
Steps to test this PR
Test

[ ] fresh install from this branch
[ ] enable NetP
[ ] verify cohort is set in ET timezone

Current dependencies on/for this PR:

develop

PR #3930   👈

This stack of pull requests is managed by Graphite.


groupby test failures on some browsers

Browser testing shows some of browser does have unexpected behavior on [test case]
(https://github.com/ReactiveX/RxJS/blob/master/spec/operators/groupBy-spec.js#L7) , like below:
Mobile Safari 7.0.0 (iOS 7.1.0) Observable.prototype.groupBy() should group numbers by odd/even FAILED
	Expected
	{"frame":20,"notification":{"kind":"N","value":"[
		{"frame":0,"notification":{"kind":"N","value":"1","hasValue":true}},
		{"frame":80,"notification":{"kind":"N","value":"3","hasValue":true}},
		{"frame":160,"notification":{"kind":"N","value":"5","hasValue":true}},
		{"frame":200,"notification":{"kind":"C","hasValue":false}}
	]","hasValue":true}}
	{"frame":60,"notification":{"kind":"N","value":"[
		{"frame":0,"notification":{"kind":"N","value":"2","hasValue":true}},
		{"frame":80,"notification":{"kind":"N","value":"4","hasValue":true}}
	]","hasValue":true}}
	{"frame":220,"notification":{"kind":"C","hasValue":false}}

	to deep equal
	{"frame":20,"notification":{"kind":"N","value":"[
		{"frame":0,"notification":{"kind":"N","value":"1","hasValue":true}},
		{"frame":80,"notification":{"kind":"N","value":"3","hasValue":true}},
		{"frame":160,"notification":{"kind":"N","value":"5","hasValue":true}},
		{"frame":200,"notification":{"kind":"C","hasValue":false}}
	]","hasValue":true}}
	{"frame":60,"notification":{"kind":"N","value":"[
		{"frame":0,"notification":{"kind":"N","value":"2","hasValue":true}},
		{"frame":80,"notification":{"kind":"N","value":"4","hasValue":true}},
		{"frame":160,"notification":{"kind":"C","hasValue":false}}
	]","hasValue":true}}
	{"frame":220,"notification":{"kind":"C","hasValue":false}}

occurs on < android 5, < IE 11, ios 7.

Is this the only test that fails or are there many?

This one's only failure under groupby so far I observed. You can see full logs in here. https://travis-ci.org/ReactiveX/RxJS/builds/105222911 . (Ignore failure under edge browser which is not test for groupby, it's covered in https://github.com/ReactiveX/RxJS/pull/1225)

@kwonoj this error makes no sense to me, specially considering that it's only one test (the simplest one) which is failing. How can I run these tests in saucelabs myself?

@staltz go to travis configuration, set SAUCE_USERNAME and SAUCE_ACCESS_KEY in your forked repo.

Ah neat. We need those instructions in CONTRIBUTING too


Documentation for DOS patterns

We need to produce guidelines for usage, creation and update of DOS patterns.

Replaced by project: https://github.com/geneontology/go-ontology/projects/16


Update README.md

"sudo" fixes the issue with "are you root" console statement

LGTM, thanks for the PR!

My pleasure!❤


Cover find by best key

Goal
Increase coverage by spec-ing Location.find_by_best_key.
Approach
Cover nil values for address1  and la_id by calling location.

Merging cause tests.


handle marks on elements with content

This is an attempt that works in a few examples I tried out. For some reason trying to use rollup locally results in an unusable dist file, so I was forced to make the changes directly in the ES5 version dist folder and here I recreate what I did here. Someone with more knowledge of the sources should take a look at it. Relates to https://github.com/ProseMirror/prosemirror/issues/780 .

Looks good so far. Could you add some tests? (This'll involve creating a throwaway schema that has such marks in the test suite—you can find an example of that in test-dom.js in the "schemaRules" test.)

Sure. I have one weird issue that makes this a bit difficult to work with: If I install the package from npmjs, I used to be able to make changes to the sources and then bundle them again like:
cd node_modules/prosemirror-model
npm install
npm run build

But when I do that now, the resulting dist/index.js creates problems when transpiling the main app, even if none of the prosemirror-model sources are changed. So what I do is manually edit dist/index.js and hope I translate everything correctly. Is there something I should need to know about the build-environment? DOes it need a certain version of node or npm for example?

the resulting dist/index.js creates problems when transpiling the main app

It would help if you could describe those problems. In principle, npm run build is also what gets run when publishing these to npm.
But even if you can't build your main app, running the package's own tests shouldn't be a problem.

It would help if you could describe those problems.

It complains about no top node for a document being defined. The error in itself doesn't really give that much of an idea of what is wrong and both transpiling of main app and of prosemirror-model work fine -- so that will require some more investigation. I just thought maybe you had recently switched to a new version of some software that would make a difference. The rollup version is defined through the package.json file, so it cannot be that.
I'll try to make the tests and then I can try to diff the dist/index.js file that I build locally and the one distributed via npm. Maybe that will give us a  clue as to what is not working as it should.

But even if you can't build your main app, running the package's own tests shouldn't be a problem.

I now realize that the tests are running using the transpiled version in the dist folder. And in my case that means that 58 of the provided test are failing, including all the DOMParser tests. I have written three test cases, but it was blindly so I'm sure there are bugs in there. The most frequent error message says:
TypeError: this.nodes[node.type.name] is not a function

I really don't get what this is. What node version are you running? And what npm version? Those are the only two components I could imagine to make a difference, even though neither one of them really should.

I upgraded to nodejs 9.11.1 with npm 5.6.0, but that didn't make any difference. Errors look like this:
60) Node from preserves a fragment:
     !eq(doc, doc(paragraph("foo"))) at from (/home/johannes/src/fiduswriter/prosemirror-model/test/test-node.js:97:7)
  Error: !eq(doc, doc(paragraph("foo")))
      at new ist.Failure (node_modules/ist/ist.js:42:11)
      at ist (node_modules/ist/ist.js:34:13)
      at from (test/test-node.js:97:7)
      at Context.it (test/test-node.js:107:8)

Have you tried deleting node_modules and reinstalling? That's the only further idea I can think of.
The implementation did not actually work, so I've written the feature anew in 5dcd186 (released as 1.4.1)

FYI, running the tests like this still fails in 58 cases for me:
git clone git@github.com:ProseMirror/prosemirror-model.git
cd prosemirror-model
npm install
npm run test


SpeedDial weird behaviour in scroll view within flex (Safari)

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When the SpeedDial is used within a scroll view, that is nested in a flex it exhibits some weird behaviour, and adversely affects the scroll view. When hovering over the SpeedDial to open it, the scroll view will be shifted down, removing any margin that may be at the bottom. If you continue to hover over the SpeedDial for a little bit the scroll view will return to normal, however hovering and quickly moving the mouse away will cause the scroll view to be stuck with the reduced height, until the SpeedDial is hovered over again.
When using with a drag and drop library, when an item is moved from the list, leaving the scroll view to move up to the remaining items, the SpeedDial will remain while the parents shift (realise drag and drop is not from this repo, however I believe it's related to the same issue)
I realise that a) This is only in Safari, which may not be fully supported. b) SpeedDial is a lab component so is not production-ready, however was hoping that someone may at least be able to shed light on why this might be happening.
Expected Behavior 🤔
The SpeedDial should not affect it's parent component, or any scroll container within which it is contained.
Steps to Reproduce 🕹
https://codesandbox.io/s/dreamy-sound-skuf3?file=/src/Demo.tsx
Steps:

Build a flex box (direction column) with a max height
Build a scroll view inside the flex box
Build a list within the scroll view, with items containing a SpeedDial (enough to ensure the list overflows)
Easiest way to see behaviour is to scroll to the bottom, and hover over the SpeedDial in the last item.

Context 🔦
I am trying to create a kanban board, where each item has a SpeedDial (in my case for reacting to the items). Each of the lanes has a header and footer which should be visible at all times (lanes will not overflow the page). The items between the header and footer should be scrollable when the lane reaches its max height.
N.B. the cards are draggable within the lists and between lists.
Your Environment 🌎

Tech
Version
Present In

Material-UI
v4.11.0
v5.0.0.alpha6

Material-UI/lab
v4.0.0-alpha.56
v5.0.0.alpha6

React
16.13.1
-

Browser
Safari (No issue in Chrome)
-

TypeScript
3.9.7
-

The speed dial is designed to be used positioned fixed. This use case is not supported


Pagination

the log files can be very long so we provide user with paginated view.
tech used-html, js, java

@googlebot I fixed it.

Resolve conflicts. Also .war files are generated files? If yes, then add it to .gitignore

@googlebot I fixed it.


[Question] Copying everything from a DOCX document to clipboard

What I would like to do, is to specify a .DOCX file, and to read all of its content by copying it into the clipboard.
Then, after opening an empty DOCX file and pasting the copied clipboard content, there should be no difference with the source document content.
How could I achieve this with python-docx?

In my experience, the Clipboard on Windows and macOS uses RTF for
transferring formatted text.  (At least, that's how I do it in my
application.)  So what you need to do is read the DOCX file, extract all
the text and formattting, convert it to RTF representation of formatted
text, and place that in the OS Clipboard with the appropriate format
flag to indicate RTF contents (which differs depending on the OS).  I
use wxPython's wx.Clipboard object to interact with the Clipboard.
You're talking about a huge amount of programming to, essentially, open
a copy of a Word file in Word.  I assume there's an interim step where
either your program or your user manipulates the data before moving on.
But in this case, you could just save the altered data as a (new) DOCx
file rather than going through the Clipboard.  That saves you from
having to write a RTF converter that mirrors all the features you need
from Word.  Maybe I'm missing something, but I don't see what involving
the Clipboard in the process really buys you.
David

What I would like to do, is to specify a .DOCX file, and to read all
of its content by copying it into the clipboard.
Then, after opening an empty DOCX file and pasting the copied
clipboard content, there should be no difference with the source
document content.
How could I achieve this with python-docx?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/python-openxml/python-docx/issues/883, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7ECDKOJQYINBISYFLWNR3SLRSRXANCNFSM4SWMEFXQ.

--
David Woods
Pronouns:  he, him, his

First of all thanks for the prompt and detailed reply.
My idea was to write a script which converts a markdown document into DOCX format by placing the results into the clipboard.
By doing so, it would be quick and easy to paste the newly formatted text directly into Outlook, Word or similar Microsoft software.
By using pandoc one could simply convert the markdown file into a DOCX document, opening it and copying the whole content, and finally pasting it in the appropriate place.
I wanted to skip the process which involved opening the file, selecting all of its content and closing the file again.


chore: simplify tools installation and management with mise

What this PR does / why we need it:

🙇 Please test locally on your machine.

❗ There is a problem with Checks / linters / lint (pull_request_target), because we use workflow from main branch and it uses third_party/go.mod that is removed in this file, so it has to be merged with by-passing and observing on main

Scope

Get rid of dir third_party and dedicated go.mod for managing tooling and all related Makefile config. Use mise to install delve from the source code (a binary is not provided).
gotestsum is handled natively
crd-ref-docs use the same approach for installation as for delve - built from source
setup-envtest is handled natively
staticcheck is handled natively
cleanup leftovers from already removed (see #6563) deprecated looppointer linter.

Which issue this PR fixes:
Follow up for https://github.com/Kong/kubernetes-ingress-controller/pull/6563

I implemented your suggestion @czeslavo and made couple of other improvements, so please check everything again


Namespaced reducers and normal reducers seems to not working both together

Hi everybody,
I have a question about redux-subspace.
I have a component that is using subspace for one reducer. It's working ok.
But another component is also using subspace for the same reducer BUT it also need another reducer.
So, it's like subspace map the state of the reducer that it manages but the other reducer is never accessible (in mapStateToProps function of my component).
I'm wondering if it exists a trick to make both normal reducer and namespaced reducers working together.
PS: I've try to sub-combine my reducers that have to work together but same sad result:
export default combineReducers({
  router: routerReducer,
  userProfile: namespaced(user, 'userProfile'),
  userSettings: namespaced(combineReducers({ user, setting }), 'userSettings'),
  user,
  signup,
  whishlist,
  setting
});

Here, the user reducer is well accessible in my component but the setting reducer functions are not available :(
Thanks
EDIT: in fact, the functions of the reducers are obvioulsy callable (because of import) but the component's props are never updated :(

Hi,
This isolation is exactly what subspace is trying to achieve, where each reducer doesn't know anything about what's around it.
So looking at your small example there, and without seeing what's in the reducers reducers and components, I'm not sure you actually need subspace at all.
But assuming you have reasons to use it we have a whole docs page on accessing "global" state that might have a few tricks for you. I'd suggest starting with wormholes (we've found them the solution to most stste sharing problems)
https://ioof-holdings.github.io/redux-subspace/docs/advanced/GlobalState.html
If you need more help setting up and using your store in these advanced configurations, feel free to ask here :)

Just based in the use of the namespaced wrapper, It looks like you are using redux-subspace v1.  Many of the global state solutions (like wormholes) only work from v2.

Thanks a lot for proposing, I need help yes. I don't know if there is another solution.
My problem is that I've my "user" reducer that expose some function like the "update" user.
export const update = request => dispatch => {
    const changeType = request.timezoneId ? 'timezone' : 'user';
    dispatch({ type: UPDATE_PENDING });
    return userService.update(request)
      .then(user => storeUserOnClient(user))
      .then(user => dispatch({ type: UPDATE_SUCCESS, user, changeType }))
      .catch(error => dispatch({ type: UPDATE_ERROR, error, changeType }));
};

These methods are coming with some actions (on the same file):
case UPDATE_PENDING:
      return {
        ...state,
        isPending: true,
        error: undefined,
        changeType: action.changeType
      };
      break;
    case UPDATE_SUCCESS:
      const user = {
        ...state.user,
        firstName: action.user.firstName,
        lastName: action.user.lastName,
        email: action.user.email
      };
      return {
        ...state,
        user,
        isPending: false,
        error: undefined,
        changeType: action.changeType
      };
      break;
    case UPDATE_ERROR:
      return {
        ...state,
        isPending: false,
        error: action.error,
        changeType: action.changeType
      };
      break;

And this reducer is declared on the index of reducers dir with some other reducers, like this:
export default combineReducers({
  router: routerReducer,
  user,
  signup,
  whishlist,
  setting
});

Component-side, I've two components that are using the reducer "user". The first one are using only the user reducers, like this:
const mapStateToProps = state => {
  return {
    user: state.user.user,
    error: state.user.error,
    isLoading: state.user.isPending,
    changeType: state.user.changeType
  };
};

const mapDispatchToProps = dispatch => bindActionCreators({ update }, dispatch);
export default connect(mapStateToProps, mapDispatchToProps)(MeProfilePage);

The second one is using the update function of the user reducer but also the setting reducers like that:
const mapStateToProps = state => {
  return {
    timezones: state.setting.timezones,
    isLoading: state.setting.isPending,
    user: state.user.user,
    error: state.user.error
  };
};

const mapDispatchToProps = dispatch => bindActionCreators({ fetchTimezones, update }, dispatch);
export default connect(mapStateToProps, mapDispatchToProps)(MeSettingPage);

The fetchTimezone is working well and my dropdown is filled by the timezone issued from my API.
The update function is also working and an http request is sent but when it returns to React, it automatically use the connected router to return to the first component that use update function. Like if router had attached the use of the update function to the first component.
I don't know if i'm clear in my explainations :(
If you need more details or if you have any idea... just tell me please.
Thanks

Sorry for the delayed response @christophedebatz, I've been on parental leave and been struggling to find time for anything.  I hope you haven't been struggling the whole time with this and found a solution or work around.
There's a lot going on in your explanation and I'm struggling to follow what the issue is and where it might be falling apart.
Are you able to set up a small codesandbox.io example that demonstrates it  for us?

Hi @mpeyper
Thanks for your reply. Don't worry about the delay!
So, I haven't found a real solution but I'm thinking on a work-around which is to create another rest endpoint to treat my http call and so to make another reducer and another action. Like this, the two pipes (the user update and the user-timezone update are separate).
I have not enough time for now to set up the problem on a js sandbox. When I'll have time, be sure you will be the first aware of!
Regards my friends.

Closing due to inactivity.  Happy to repoen if there is more discussion to be had.


[ci] Increase timeouts in Verilator simulation

Since several days we regularly hit the boot timeout in
VerilatorSimOpenTitan.assert_selfchecking_test_passes, which used to
be 120s (2 minutes). Double this timeout to 4 minutes.
To avoid the next betch of timeouts, also double the overall test
timeout to 20 minutes.

@imphil thanks!


Converted setup to use poetry completely.

Hey Georg,
I recently wanted to start using the repo and was having some trouble integrating it with poetry because it required ssh in order to install. I suspect this is because in the requirements doc the torchlambertw package was installed via ssh and therefore required this package to do so as well. To make it more installable, I just changed it so people can install with http instead.
In addition, I just converted the build to use poetry and not rely on setuptools anymore and I also simplified the pre-commit config. Finally, just to make the dev setup more universal, I added in a devcontainer spec so anybody can just quickly set up the repo and make any PRs.
Let me know what you think and if there are any changes you might need! For now, I'm just going to be installing from my forked version until you have some time to take a look at the PR.
Thanks,
Matt
Edit:

reverted changes to pre-commit file

Approved; run a re-base to pick up on latest changes (i fixed igmm.py as well and added CI/CD worfklow). might require a change with the poetry setup


chore(requirejs): perserve licenses

creating sourcemaps removes licenses. manually add them back...

This is a problem using r.js but the licences are kept within the js.map files so I think its fine.


Fix the phylogeny spacing bug

A bug in the current code causes all phylogenies to share the same spacingX and spacingY variables. This PR updates the code to ensure that spacingX and spacingY can be modified on a per-phylogeny basis, and adds a test to ensure that spacingX and spacingY can be set individually for each phylogeny.
Ready for review!

I've added changePhylogenySpacingX/Y functions to replace manipulating phylogenySpacingX/Y[phylogeny] directly. I think the code looks better!
@hlapp Could I annoy you to have another look at them and let me know if you think it's clearer now?


[Help wanted] Scroll in floaterm

Is it possible to scroll output in floaterm?
I run neovim from Alacritty so neither Vi mode nor S+Pg Up (Down) is working.
Maybe there is a way to bind scroll in floaterm on different keys?

it's possible. but i wonder how about exit to normal mode then scroll

Through Shift + Pg up? It doen't work.

I will take a look at this. maybe fix in next version. currently I am working on neovim core. please patience.

Sure!

Also want to know how to scroll in the float window of hover_doc~~


feat(mocha-runner): improve Mocha support

closes #1046

[x]use your mocha.opts file by default (if exists)
[ ]  Make sure relative imports when using --require (same as mocha does it)
[ ]  Make sure const { describe } = require('mocha'); works as well.

Looks great! Thanks again!


Imageactions

Some new actions based on selected elements:
a) Render the selected elements and cut the image into multiple pieces to allow for separate burning (or whatever) of oversized stuff

b) Create keyhole images by selecting elements plus an additional element that will act as mask or keyhole for the other elements

Hm. At least we can hem and haw over adding new features also "alignment" this is part of alignment tools?


Improve the HTTP data binding BBE to make use of all the fields in the bound record

Description:
$title as mentioned in https://ballerina-platform.slack.com/archives/C47EAELR1/p1568910584038800 -
https://github.com/ballerina-platform/ballerina-lang/blob/master/examples/http-data-binding/http_data_binding.bal#L7 is not used.
Would be useful to demonstrate chained access using the map (or maybe we could make that a record too).

Fixed via https://github.com/ballerina-platform/ballerina-lang/pull/19661, hence closing


Added test for regression on module import

Tests to be fixed

[x]  TuriTests.test_top_level
[ ] TabCompleteVisibilityTests.test_churn_predictor
[ ] TabCompleteVisibilityTests.test_kmeans
[ ] TabCompleteVisibilityTests.test_local_outlier_factor
[ ] TabCompleteVisibilityTests.test_search
[ ] TabCompleteVisibilityTests.test_supervised
[ ] TabCompleteVisibilityTests.test_topic_model
[ ] ModuleVisibilityTests.test_Image_type
[ ] ModuleVisibilityTests.test_anomaly_detection
[ ] ModuleVisibilityTests.test_churn_predictor
[ ] ModuleVisibilityTests.test_classifier
[ ]  ModuleVisibilityTests.test_cross_validation
[ ] ModuleVisibilityTests.test_data_matching
[ ] ModuleVisibilityTests.test_feature_engineering
[ ] ModuleVisibilityTests.test_graph_analytics
[ ] ModuleVisibilityTests.test_lead_scoring
[ ] ModuleVisibilityTests.test_models_with_hyper_parameters
[ ] ModuleVisibilityTests.test_nearest_neighbors
[ ] ModuleVisibilityTests.test_recommender
[ ] ModuleVisibilityTests.test_text_analytics
[ ] ModuleVisibilityTests.test_toolkits
[ ] ModuleVisibilityTests.test_topic_model
[ ] ModuleVisibilityTests.test_topic_modelling_models

Great job. The python import is such a tricky part. Let me find out who introduced config.
for other missing pieces:
run  ipython3 -c "import turicreate as tc; dir(tc)" >> foo.txt on both pypi turicreate and local turicreate with lazy import:
>  '_LazyCallable',
>  '_LazyModuleLoader',
31a34
>  'audio_analysis',
36d38
<  'config',
87c89
<  'topic_model',
---
>  'topci_model',

you catch the topic model, still I forget audio_analysis and config.

minor fix: you need to add config and possibly remove audio_analysis since it's not in 5.6. Surprisingly, audio_analysis is not in our public api and does it mean no user?

@Jarvi-Izana https://github.com/apple/turicreate/pull/2352
Fixes the config import. Not sure about audio_analysis, if that was something you introduced accidentally or is actually an expected feature.

the lazy module loader will hide the import of tc.config since all the toolkit imports below are deferred.
src/unity/python/turicreate/toolkits/image_classifier/image_classifier.py
22:from turicreate import config as _tc_config

src/unity/python/turicreate/toolkits/object_detector/object_detector.py
28:from turicreate import config as _tc_config

src/python/turicreate/util/__init__.py
30:    import configparser as _ConfigParser
32:    import ConfigParser as _ConfigParser

src/python/turicreate/toolkits/image_classifier/image_classifier.py
22:from turicreate import config as _tc_config

src/python/turicreate/toolkits/object_detector/object_detector.py
28:from turicreate import config as _tc_config

let's make those implicit imports as explicit imports, as python zen suggested.

great work! amazed!

It's really difficult to see what has changed in the test file. Next time please use git mv to rename the test file.

Can this be merged?

test failure due to the implicit import.


Add text-align left to control panel container

I put a control-panel on a center-aligned page and it took me a while to figure out why the layout was all wrong. It inherited the center alignment. So I added text-align: center to the control panel. There are probably more props that need to be specified so that it doesn't inherit the wrong properties, but this is a start!

Sorry to lump in more with this, but while I was tweaking container styles, also added box-sizing: border-box to the main container since if you request width: 400, the width is always greater than 400, which is a little annoying. This makes width = 400 if you request width = 400.


Fix incorrect sky rotation based on camera axis

Should fix https://github.com/godotengine/godot/issues/56136

Out of curiosity, why does changing the order helps? How is it possible?

Out of curiosity, why does changing the order helps? How is it possible?

Order is matter for matrixes: https://en.wikipedia.org/wiki/Matrix_multiplication#Non-commutativity

Oh, so these are matrixes, I see, thanks!


Cannot connect

Hi
Thanks for creating this package. I cannot get working due to connection error. I get following messages from debug output in node-red.
"No chirpstack connection set"
"TypeError: Cannot read property 'fullAddress' of null"
I am running node-red in docker container and have no problems accessing the chirp-stack server via POST/GET API from node-red.
I have obviously entered my server and login details in the node configuration. Any tips please?
Thanks.

this is very strange, somehow it looks like the configuration node is not saved correctly. Can u share a screenshot of your host and port (optionaly foo bar'ed)

this is very strange, somehow it looks like the configuration node is not saved correctly. Can u share a screenshot of your host and port (optionaly foo bar'ed)

I just revieuwed the code, it looks like the node where you are trying to do a call has no connection set. Therefor the error "No chirpstack connection set". Can you check all chirpstack nodes and verify if all connections are set to your configuration node.

I just revieuwed the code, it looks like the node where you are trying to do a call has no connection set. Therefor the error "No chirpstack connection set". Can you check all chirpstack nodes and verify if all connections are set to your configuration node.

Thanks for looking into this. Here are screenshots of my connection details. They seem persistent.

Thanks for looking into this. Here are screenshots of my connection details. They seem persistent.

A little more information on the console:
6 Jan 18:37:28 - [error] [chirpstack-connection:2848480d.26c988] TypeError: Channel's second argument (credentials) must be a ChannelCredentials
6 Jan 18:37:28 - [error] [chirpstack-user-management:listUsers] No chirpstack connection set
6 Jan 18:37:28 - [error] [chirpstack-device-management:2fa94562.21dd82] No chirpstack connection set

A little more information on the console:
6 Jan 18:37:28 - [error] [chirpstack-connection:2848480d.26c988] TypeError: Channel's second argument (credentials) must be a ChannelCredentials
6 Jan 18:37:28 - [error] [chirpstack-user-management:listUsers] No chirpstack connection set
6 Jan 18:37:28 - [error] [chirpstack-device-management:2fa94562.21dd82] No chirpstack connection set

I reinstalled the nodes and the problem has resolved. Can now connect successfully. Not sure what the issue was.

I reinstalled the nodes and the problem has resolved. Can now connect successfully. Not sure what the issue was.

I'm not sure either what happened. Good that you got it working. Have fun with it, and if you have any more issues or suggestions let me know!

I'm not sure either what happened. Good that you got it working. Have fun with it, and if you have any more issues or suggestions let me know!


Gam Info domain doesn't show the latest data

Gam info domain doesn't show the latest data of licenses info.
Do let me know if there is an alternative option to check the updated license info.

gam print licenses will show latest license data. gam info domain shows latest cumultative info as the reports API gives GAM (which can be outdated)


adjust userriskprofile.update's null date handling

Description of Change
sdk.userriskprofile.update() when getting None or "" for end_date or start_date was sending:
{"startDay": {"day": null, "month": null, "year": null}

This was causing errors on the backend trying to parse the date values.
To clear the value (or when not updating at all), we need to send just:
{"startDay": null}

Looks like the unit tests just need to be adjusted


Codeception 2.1

Updated Codeception up to 2.1.x
Removed not needed old files (test-related)
Fixed functional tests
Removed PHPUnit (Codeception already contains PHPUnit)
Updated dependencies

:+1:


math.Float32frombits don't support interface{}

Hi, in the following codes, i expect to get 8, but i got 1.1e-44 instead.   I think the problem is caused by the unsafe pointer inside math.Float32frombits function.  I don't know if it's a feature or bug. I really hope we at least can get some warning information when compile following codes.
package main
import (
	"fmt"
	"math"
)

func main() {
	var x interface{}
	x = uint32(8)

	fmt.Println(math.Float32frombits(x.(uint32)))
}

I just figure it out, the number 8 need to be convert to hexadecimal 0x41000000. kind of weird. Issue closed.

0x41000000 is how 8 is written in IEE754 float32, so that's not that surprising. Float32frombits is a rather low-level function that works directly on the value's bit representation in memory.


Add NNX support for legacy jax.random.PRNGKey()

Currently, it doesn't seem possible to straightforwardly checkpoint (with Orbax) an NNX module that includes random keys (like with dropout), see https://github.com/google/orbax/issues/1105#issue-2488663946. This seems to be due to the new JAX random key type (https://jax.readthedocs.io/en/latest/jep/9263-typed-keys.html), which is used here (https://github.com/google/flax/blob/fc19c5dcc136b17d7a2c406831126d93bbdac6d7/flax/nnx/rnglib.py#L186) in NNX. Although Orbax has added individual support for the new type (see https://github.com/google/orbax/issues/620), saving nnx.state(model) that includes dtype=key<fry> doesn't seem to be possible.

Hey @cisprague, maybe you can convert to the old format before serializing?
You could use something like:
def get_key_data(x):
  # use jax.random.key_data

state = jax.tree.map(get_key_data, state)

See PRNGKeys

Following Cristian's recommendation, FWIW, this worked for me until the core issue is resolved.
# saving
_, state = nnx.split(model)

state = jax.tree.map(
    lambda x: jax.random.key_data(x) if x.dtype.name == "key<fry>" else x,  # ☹
    state
)

checkpoint_manager.save(0, args=ocp.args.StandardSave(state))

# restoring
abstract_model = nnx.eval_shape(lambda: model)

graphdef, abstract_state = nnx.split(abstract_model)

abstract_state = jax.tree.map(
    lambda x: None if x.dtype.name == "key<fry>" else x,
    abstract_state
)

res = checkpoint_manager.restore(0, args=ocp.args.StandardRestore(abstract_state))

model = nnx.merge(graphdef, res["state"])


inline function uses a private function is a compile error but IDE doesn't show it

Repro:
module InlineTest =
    let private innerFunc x = x + 1
    let inline inlineFunc x = (innerFunc x) + 1

[<EntryPoint>]
let main _argv =
    InlineTest.inlineFunc 7 |> ignore
    0

It expectedly gives a compilation error:
Program.fs(3, 16): [FS1113] The value 'inlineFunc' was marked inline but its implementation makes use of an internal or private function which is not sufficiently accessible
But the IDE doesn't highlight the error (Rider 2021.1.3)

Thanks for the report! It looks like it's about FCS https://github.com/dotnet/fsharp/issues/11677


Consider adding a check for trailing slash in  this.urlRoot

Is your feature request related to a problem? Please describe.
The API I use doesn't accept trailing slashes. Thus, the default string concatenation in url() doesn't work for me.
https://github.com/coinbase/rest-hooks/blob/17bc481aa2b55ebe087d7fdecd663f6a528f0cf6/src/resource/Resource.ts#L174
Describe the solution you'd like
A simple if can check if the last character of this.urlRoot is a slash and act accordingly.
Describe alternatives you've considered
I'm currently overriding url as a workaround. I think my use case is common enough to be contributed upstream, as explained above.
I can provide a PR if there is interest.

Sounds reasonable, I would love to see this PR. Thanks for the contribution :)


Add new bindgen tool for Haskell and Rust

This adds a new binary tool users can use to automatically generate
imports for Haskell or Rust libraries without having to parse and write
it themselves.
Right now this only supports Haskell to Rust and doesn't account for
things like improper Types and assumes valid syntax.
Example:
foreign export ccall hello :: I64 -> I64 -> I32
foreign export ccall goodbye :: I64 -> I32
gets turned into the output of
extern {
pub fn hello(a: I64, b: I64) -> I32;
pub fn goodbye(a: I64) -> I32;
}
Note this doesn't include linking or anything like that but it's a good
start for the tool.
@nanotech give it a whirl and let me know what you think.
in the hrgen directory call:
cargo run -- -h Test.hs

To have it run.

Nice! I was thinking of doing this in Haskell so I could use haskell-src-exts, but since we only need to parse types, a full language parser isn't needed (and Haskell types are easy to parse). The next step would be to switch to a parser combinator library like nom or combine so nested function types and parameterized types can be parsed correctly and simply.
For parsing Rust, using syntex (or maybe syn?) is probably the easiest approach.

@nanotech I've wanted to get familiar with nom so that would be fun to use. syntex would be good for parsing Rust. I'll have to look into it more. We definitely want to switch to a parser library though. This was a nice little proof of concept.

I'm going to merge this into master so any changes can be made from there if you want to play around with it more. I think I'm going to get the basic form in for Rust though parsing it will be a bit harder.


Relax Sized bound

Currently it's not possible to get the name of unsized types, eg. dyn Trait.

Heya, I've implemented this and released it in 0.1.5:
assert_eq!(tynm::type_name::<dyn core::fmt::Debug>(), "dyn Debug");

Nice, thanks 👍


Oops! Something went wrong.

Hi, I am trying to install Youtube-dl-web, but I always get this error:
Oops! Something went wrong. Make sure the website is supported by youtube-dl.
It's the same error that on your demo page: http://jaimemf.github.io/youtube-dl-web/. It seems to be an communication error with the Api. Is there anything broken ?
Thanks

how do i setup my own youtube-dl-api-server ? i need a more detailed instruction i am running a vps plesk 12 centos 6.9. do i need to create a subdomain and host it on this?


Provide a way to get results from messages

We use a "fire-and-forget" actor model for dispatching messages. This has some large security benefits and avoids a few classes of bugs from ethereum, notably re-entrancy attacks, which are very tricky to defend against. However, sometime we do want a return value from a function - like when we create an object with an auto-incremented ID and want to save that ID in the caller.
There is one solution to this, which we can see when using IBC. The rough flow is:

Caller commits an intermediate state (eg locks to-be-sent coins in an escrow)
Caller dispatches IBC message
Sometime later, the receiving chain processes the message and returns a Result
Even later, the original contract gets an "ibc_ack" with an identifier of the original message and the result of execution. It can use that to look up the intermediate state and commit it or roll it back.

This does run over multiple transactions and multiple chains. We could simplify this somewhat to allow callbacks in the same TX:

Caller makes updates and dispatches a message, message contains callback: Option<HumanAddr>.
Callee processes tx, then dispatches a custom response message to the contract address listed in callback if set
Original contract gets the callback info and somehow knows what to update.

How we handle identifiers and callbacks needs plenty of specification, but I think that rough flow could work if both sides are designed for it. We need to finalize a design for the low-level api and add some helpers to make this easier to work with.

Superseded by https://github.com/CosmWasm/cosmwasm/issues/691 and done


Undisclosed Forge version requirement

The Foundry Forge version requirement is unknown. Foundry Forge does not have a versioning scheme, only a git tag.
Therefore, it would be best to know which versions (using dates or commit tags) to understand which version of Foundry Forge is compatible with the plugin.

In v0.2.0 of this plugin (see Releases), we introduced a requirement on forge-std v1.8.0.  These kinds of requirements are reflected as breaking changes in the changelog and using semantic versioning.  This is the only version requirement that I am aware of -- please let me know if you notice any other unexpected requirement.
I agree the documentation can be improved to make this requirement clearer, and will plan to add that.

Update readme and docs in https://github.com/OpenZeppelin/openzeppelin-foundry-upgrades/pull/38 to clarify the above, and this will be included in the docs site via https://github.com/OpenZeppelin/openzeppelin-upgrades/pull/1005


Speed up slow seeders

Some of our seeders are running pretty slow. Especially the UserSeeder & TagSeeder. It would be great if the total time to run the seeders was just a few seconds.
Seeding: Database\Seeders\UserSeeder
Seeded:  Database\Seeders\UserSeeder (16,042.36ms)
Seeding: Database\Seeders\TagSeeder
Seeded:  Database\Seeders\TagSeeder (15,695.38ms)
Seeding: Database\Seeders\ReplySeeder
Seeded:  Database\Seeders\ReplySeeder (1,791.61ms)
Seeding: Database\Seeders\NotificationSeeder
Seeded:  Database\Seeders\NotificationSeeder (3,499.28ms)
Seeding: Database\Seeders\LikeSeeder
Seeded:  Database\Seeders\LikeSeeder (916.51ms)

Seems to still be quite slow for me after the PR from above:
Dropped all tables successfully.
Migration table created successfully.
Loading stored database schema: /Users/driesvints/Sites/laravel.io/database/schema/mysql-schema.dump
Loaded stored database schema. (175.46ms)
Migrating: 2021_10_31_143501_add_declined_at_column_to_articles_table
Migrated:  2021_10_31_143501_add_declined_at_column_to_articles_table (15.95ms)
Seeding: Database\Seeders\UserSeeder
Seeded:  Database\Seeders\UserSeeder (690.16ms)
Seeding: Database\Seeders\TagSeeder
Seeded:  Database\Seeders\TagSeeder (18,051.48ms)
Seeding: Database\Seeders\ReplySeeder
Seeded:  Database\Seeders\ReplySeeder (1,783.14ms)
Seeding: Database\Seeders\NotificationSeeder
Seeded:  Database\Seeders\NotificationSeeder (3,244.01ms)
Seeding: Database\Seeders\LikeSeeder
Seeded:  Database\Seeders\LikeSeeder (806.98ms)
Database seeding completed successfully.


Re-check all file format loaders for derived coordinate units

Following this comment
Since all Coords now default to units=None (translating to "unknown"),
whereas before the default was '1',
We should check creation of Aux Factories in all the file-loading code to ensure that sensible units are assigned wherever needed.
This also applies to iris-grib.

I checked this, and I think it has been handled everywhere relevant in both iris + iris-grib.
Notes:
It only applies in formats pp(+ff), netcdf and grib.
In all cases, factories are created programmatically from coords which were already created elsewhere.
We need to ensure that all those have the appropriate units.
That seems to be already all done :

For the field-based formats, every coord is created with specific units.
For netcdf, a constituent coord can only be assigned the default units ('unknown') if the netcdf var had no units attribute,
but that would be a CF error in itself, so the file would be "bad".

The last case might have been missed previously, as we used to assume units of 1, but we don't need to support this anyway.
#3870 suggests  a whatsnew note about this


Feature/aws sso

New changes are made as per requirements  and added steps for Mac Os

@bbsahoobyndr  can we remove windows only reference:


Seeing through blocks

Hello whenever i try and use the mod, it never fully loads and many blocks end up being invis

ible.

You are probably use Sodium and/or Nvidium mod. Read the README on GitHub or description on ModRinth


Customizeable actions?

Can we make (for example) the trash operation customizable?
I use a custom written trash command.
For now it is hardcoded:
https://github.com/dylanaraps/fff/blob/master/fff#L71
Also wondered if I could easy add my own actions? I would love to add "send-by-mail" and alike without modifying this source too much.
If you say this is going to kill the purpose of fff I am fine with that as well.
Thanks and have a nice day!

This won’t be hard to do at all (I’ve got it almost working locally in a separate branch).
I’ll get to it.

I'd also love to see this feature. Would be great if you could also unbind the default actions.
Can you maybe push the branch on github?
I freaking love this tool btw, and I think it has a great potential to be used in scripts as abstract file selector similar to e.g. dialog --fselect.

Yes this would be fantastic, sometimes I want to open files directly in the browser but there's no way to specify custom commands to custom bindings.

I've been thinking about it for a while and haven't figured out the right way to do it. I will get to it soon.


DOC-2821 ECS Task Definition ARN doc

https://harness.atlassian.net/browse/DOC-2821
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ x] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/DOC-2821

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://hdh.pr.harness.io/pr-1073

Preview environment: https://hdh.pr.harness.io/pr-1073


Update gatsby dependency to v3

Thanks for the pull request!
It still needs some fixes to work with the specified theme-ui version. Also, as this requires a new major version for the theme, I am going to make a few more changes to benefit from new features. I'll keep track of the progress here.

[ ] update to Emotion 11 required by theme-ui
[ ] theme-ui: adjust to new color modes
[ ] theme-ui: rename Styled to Themed
[ ] update React to ^17.x.x to use jsxImportSource instead of old JSX Pragma
[ ] update react-netlify-forms
[ ] check if @mdx-js/react is still needed and remove if not

New version 3.0.0 now uses Gatsby v3.
(Checks failed because of current monorepo setup not resolving to the local package version but instead uses the NPM published one - nothing to do with the changes here)


Issue during install?

`ice@nobody-hq:~/misskey$ sudo docker-compose run --rm web yarn run init
Creating misskey_web_run ... done
yarn run v1.22.17
$ npm run migrate

<EMAIL_ADDRESS>migrate
cd packages/backend && npx typeorm migration:run -d ormconfig.js

Error during migration run:
Error: Unable to open file: "/misskey/packages/backend/ormconfig.js". bad indentation of a mapping entry (52:4)
49 |
50 |   # Extra Connection options
51 |   #extra:
52 |    ssl: true
---------^
53 |
54 | #   ┌─────────────────────┐
at Function.loadDataSource (/misskey/packages/backend/node_modules/typeorm/commands/CommandUtils.js:22:19)
at async Object.handler (/misskey/packages/backend/node_modules/typeorm/commands/MigrationRunCommand.js:34:26)
npm notice
npm notice New minor version of npm available! 8.3.1 -> 8.10.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.10.0
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: 1
ice@nobody-hq:~/misskey$ npm -v
8.10.0
`

If you encoutered a problem during install misskey, at first, please ask it on Misskey Official Discord( https://discord.gg/Wp8gVStHW3 ) or Misskey Forum( https://forum.misskey.io ). Even if you ask it on these places and can' solve your installation problem, making an issue on misskey-dev/missky repository( https://github.com/misskey-dev/misskey ) is recommended.
This repo is specialized for Misskey-hub( Misskey Official Website ).


update Readme with correct credential setup instructions #84

Contributes to #85
What did you do?
Fixed instructions on where to get the credentials from.
Why did you do it?
Instructions were broken. Discussed the fix with the team.
How have you tested it?
Yes
Were docs updated if needed?

[ ] No
[x] Yes
[ ] N/A

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new console logs
[x] Fixes entire issue
[ ] Partial fix for issue

@hcemk I asked for a small change. Additionally, you need to fix the DCO part. Please follow the instructions by clicking on Details under the failed DCO test.

@upkarlidder comments addressed, please review


Textadept 9.5 beta: core/lfs_ext.lua: "attempt to compare number with string"

I get the following error with Textadept 9.5 beta on Ubuntu 17.04:

/opt/textadept/core/lfs_ext.lua:97: attempt to compare number with string

It occurs whenever opening a .nim file or pressing Ctrl-Space, etc.
This is my first time trying Textadept, so I apologize if this is a simple Textadept issue.  I tried it specifically because I came across this Nim plugin.  I am very much hoping for a lighter and more portable alternative to vscode with full Nim support.  Thank you very much for your efforts!  :+1:

Thank you for the report! This issue lies in lack of backward compatibility between textadept versions. Please check if it is fixed now.

Well I am closing the issue due to no response. I can not reproduce it after the fix, so it may be considered as fixed.


Map not visible after v-show

"vue3-openlayers": "0.1.*",
Hiding the map with v-show results in a blank canvas and error message [Warning] No map visible because the map container's width or height are 0. (vue-0eab179a9c5c1648c422.js, line 51744) when show = true
Not sure what to do about this; is this a bug or is there something to do ?
<ol-map
        ref="olMap"
        :key="uid+'-map'"
        class="ol-map-wrapper"
        :default-interactions="interactionOptions"
        style="height: 350px; width: 720px"
        v-on:mousedown="disableUpdate"
        v-on:mouseup="enableUpdate"
    >

calling olMap.value.map.updateSize() solves the visibility issue but I still have the warning

I could not reproduce this. There is no error in the console when the visibility changed.
You can review my example :https://codesandbox.io/s/v-show-warning-yvk7b?file=/src/components/Comp.vue


feat: add ginkgolinter

Description
add ginkgolinter to golangci lint and apply suggested fixes
Issue ticket number and link
RHTAP-1435
Type of change

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

How Has This Been Tested?
ginkgolinter ./...

Checklist:

[X] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/test redhat-appstudio-e2e


pshell doesn't compile on SDK 2.0.0 targetting Pico

When trying to compile https://github.com/lurk101/pshell (1.2.30) using SDK 2.0.0 and ARM GCC 13.3.1 targetting Pico and some definitions are unavailable:
In file included from W:\pshell\cc\cc.c:251:
W:\pshell\cc\cc_defs.h:23:23: error: 'GPIO_FUNC_XIP' undeclared here (not in a function); did you mean 'GPIO_FUNC_SIO'?
   23 |     {"GPIO_FUNC_XIP", GPIO_FUNC_XIP},
      |                       ^~~~~~~~~~~~~
      |                       GPIO_FUNC_SIO
W:\pshell\cc\cc_defs.h:77:17: error: 'clk_rtc' undeclared here (not in a function); did you mean 'clk_adc'?
   77 |     {"clk_rtc", clk_rtc},
      |                 ^~~~~~~
      |                 clk_adc
W:\pshell\cc\cc_defs.h:85:26: error: 'PICO_DEFAULT_I2C_INSTANCE' undeclared here (not in a function)
   85 |     {"i2c_default", (int)PICO_DEFAULT_I2C_INSTANCE},
      |                          ^~~~~~~~~~~~~~~~~~~~~~~~~
W:\pshell\cc\cc_defs.h:92:26: error: 'PICO_DEFAULT_SPI_INSTANCE' undeclared here (not in a function)
   92 |     {"spi_default", (int)PICO_DEFAULT_SPI_INSTANCE},
      |                          ^~~~~~~~~~~~~~~~~~~~~~~~~
W:\pshell\cc\cc_defs.h:109:21: error: 'TIMER_IRQ_0' undeclared here (not in a function); did you mean 'TIMER1_IRQ_0'?
  109 |     {"TIMER_IRQ_0", TIMER_IRQ_0},
      |                     ^~~~~~~~~~~
      |                     TIMER1_IRQ_0
W:\pshell\cc\cc_defs.h:110:21: error: 'TIMER_IRQ_1' undeclared here (not in a function); did you mean 'TIMER1_IRQ_1'?
  110 |     {"TIMER_IRQ_1", TIMER_IRQ_1},
      |                     ^~~~~~~~~~~
      |                     TIMER1_IRQ_1
W:\pshell\cc\cc_defs.h:111:21: error: 'TIMER_IRQ_2' undeclared here (not in a function); did you mean 'TIMER1_IRQ_2'?
  111 |     {"TIMER_IRQ_2", TIMER_IRQ_2},
      |                     ^~~~~~~~~~~
      |                     TIMER1_IRQ_2
W:\pshell\cc\cc_defs.h:112:21: error: 'TIMER_IRQ_3' undeclared here (not in a function); did you mean 'TIMER1_IRQ_3'?
  112 |     {"TIMER_IRQ_3", TIMER_IRQ_3},
      |                     ^~~~~~~~~~~
      |                     TIMER1_IRQ_3
W:\pshell\cc\cc_defs.h:115:17: error: 'XIP_IRQ' undeclared here (not in a function); did you mean 'OTP_IRQ'?
  115 |     {"XIP_IRQ", XIP_IRQ},
      |                 ^~~~~~~
      |                 OTP_IRQ
W:\pshell\cc\cc_defs.h:124:23: error: 'SIO_IRQ_PROC0' undeclared here (not in a function)
  124 |     {"SIO_IRQ_PROC0", SIO_IRQ_PROC0},
      |                       ^~~~~~~~~~~~~
W:\pshell\cc\cc_defs.h:125:23: error: 'SIO_IRQ_PROC1' undeclared here (not in a function)
  125 |     {"SIO_IRQ_PROC1", SIO_IRQ_PROC1},
      |                       ^~~~~~~~~~~~~
W:\pshell\cc\cc_defs.h:134:17: error: 'RTC_IRQ' undeclared here (not in a function); did you mean 'OTP_IRQ'?
  134 |     {"RTC_IRQ", RTC_IRQ},
      |                 ^~~~~~~
      |                 OTP_IRQ
In file included from W:\pshell\cc\cc.c:425:
W:\pshell\cc\cc_extrns.h:33:37: error: 'clocks_init' undeclared here (not in a function); did you mean 'clocks_hw_t'?
   33 |     {"clocks_init", 0, clk_defines, clocks_init, 0, 0, 0},
      |                                     ^~~~~~~~~~~
      |                                     clocks_hw_t
W:\pshell\cc\cc_extrns.h:100:38: error: 'i2c_hw_index' undeclared here (not in a function); did you mean 'i2c_get_index'?
  100 |     {"i2c_hw_index", 1, i2c_defines, i2c_hw_index, 0, 0, 0},
      |                                      ^~~~~~~~~~~~
      |                                      i2c_get_index

Manually hardcoding values allowes it to compile. But the switching to Pico2 and ARM and:
[  4%] Linking CXX executable pshell_usb.elf
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
Binary info must be in first 256 bytes of the binary
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj: in function `gen':
W:\pshell\cc/cc.c:2877:(.text.gen+0x5e4): undefined reference to `__wrap___aeabi_fcmple'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:2877:(.text.gen+0x5e8): undefined reference to `__wrap___aeabi_fcmpge'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:2892:(.text.gen+0x1088): undefined reference to `__wrap___aeabi_fsub'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:2892:(.text.gen+0x108c): undefined reference to `__wrap___aeabi_idiv'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:2892:(.text.gen+0x1090): undefined reference to `__wrap___aeabi_fadd'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:2892:(.text.gen+0x1094): undefined reference to `__wrap___aeabi_fmul'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:2892:(.text.gen+0x1098): undefined reference to `__wrap___aeabi_fdiv'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:2892:(.text.gen+0x10a4): undefined reference to `__wrap___aeabi_f2iz'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:2892:(.text.gen+0x10a8): undefined reference to `__wrap___aeabi_i2f'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj: in function `cc':
W:\pshell\cc/cc.c:4298:(.text.cc+0x970): undefined reference to `__wrap___aeabi_idiv'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:4298:(.text.cc+0x978): undefined reference to `__wrap___aeabi_i2f'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:4298:(.text.cc+0x980): undefined reference to `__wrap___aeabi_f2iz'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:4298:(.text.cc+0x988): undefined reference to `__wrap___aeabi_fadd'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:4298:(.text.cc+0x990): undefined reference to `__wrap___aeabi_fsub'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:4298:(.text.cc+0x998): undefined reference to `__wrap___aeabi_fmul'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:4298:(.text.cc+0x9a0): undefined reference to `__wrap___aeabi_fdiv'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:4298:(.text.cc+0x9a8): undefined reference to `__wrap___aeabi_fcmple'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:4298:(.text.cc+0x9b0): undefined reference to `__wrap___aeabi_fcmpge'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:4298:(.text.cc+0x9b8): undefined reference to `__wrap___aeabi_fcmpgt'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
W:\pshell\cc/cc.c:4298:(.text.cc+0x9c0): undefined reference to `__wrap___aeabi_fcmplt'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0x4): undefined reference to `__wrap___aeabi_idiv'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0x8): undefined reference to `__wrap___aeabi_i2f'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0xc): undefined reference to `__wrap___aeabi_f2iz'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0x10): undefined reference to `__wrap___aeabi_fadd'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0x14): undefined reference to `__wrap___aeabi_fsub'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0x18): undefined reference to `__wrap___aeabi_fmul'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0x1c): undefined reference to `__wrap___aeabi_fdiv'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0x20): undefined reference to `__wrap___aeabi_fcmple'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0x24): undefined reference to `__wrap___aeabi_fcmpgt'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0x28): undefined reference to `__wrap___aeabi_fcmplt'
E:/Download/Pico_2/arm-gnu-toolchain-13.3.rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe:
CMakeFiles/pshell_usb.dir/cc/cc.c.obj:(.rodata.fops+0x2c): undefined reference to `__wrap___aeabi_fcmpge'
collect2.exe: error: ld returned 1 exit status
mingw32-make[2]: *** [CMakeFiles\pshell_usb.dir\build.make:1450: pshell_usb.elf] Error 1
mingw32-make[1]: *** [CMakeFiles\Makefile2:2287: CMakeFiles/pshell_usb.dir/all] Error 2
mingw32-make: *** [makefile:102: all] Error 2

Obviously building in separate dirs.

These look like issues with that project. You should probably raise an issue there?

To be honest, it was motivated only to improve SDK if there is an issue. BTW, it compiles on SDK 1.5.1 just fine.

To be honest, it was motivated only to improve SDK if there is an issue.

https://github.com/raspberrypi/pico-sdk/releases/tag/2.0.0 has a big list of things that have changed in the latest SDK release.

Sounds fair, my bad.

Note those errors at the top should not happen - you started with clean directory for RP2040 too? it looks like you have a mix of old / new setup.
There is a change listed in the release notes: PICO_DEFAULT_XXX_INSTANCE is now PICO_DEFAULT_XXX_INSTANCE()

Yes, there was a mixup - that first error list was from Pico2, Pico on SDK 2.0.0 outputs only:
In file included from ../cc/cc.c:251:
../cc/cc_defs.h:85:26: error: 'PICO_DEFAULT_I2C_INSTANCE' undeclared here (not in a function)
   85 |     {"i2c_default", (int)PICO_DEFAULT_I2C_INSTANCE},
      |                          ^~~~~~~~~~~~~~~~~~~~~~~~~
../cc/cc_defs.h:92:26: error: 'PICO_DEFAULT_SPI_INSTANCE' undeclared here (not in a function)
   92 |     {"spi_default", (int)PICO_DEFAULT_SPI_INSTANCE},
      |                          ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ../cc/cc.c:425:
../cc/cc_extrns.h:33:37: error: 'clocks_init' undeclared here (not in a function); did you mean 'clocks_hw_t'?
   33 |     {"clocks_init", 0, clk_defines, clocks_init, 0, 0, 0},
      |                                     ^~~~~~~~~~~
      |                                     clocks_hw_t
../cc/cc_extrns.h:100:38: error: 'i2c_hw_index' undeclared here (not in a function); did you mean 'i2c_get_index'? C object CMakeFiles/pshell_usb.dir/
  100 |     {"i2c_hw_index", 1, i2c_defines, i2c_hw_index, 0, 0, 0},
      |                                      ^~~~~~~~~~~~
      |                                      i2c_get_index

and PICO_DEFAULT_XXX_INSTANCEs are easily fixable with new definitions. Just compiling some examples on a RAM partition - starting with empty partition and to be sure, downloaded it again.

Ah gotcha - yes we have new macros you can use which work across both ro2040 and rp2350  whrrre there are different numbers of instances/irqs on the two chips - check release notes


Warning: optional content group not found: 10r

Not displaying pdf with this error message. Maybe missing layers? Maybe extra margin? Maybe corrupted? Should at least display error message. Workaround is to open in Inkscape and export fit to page.

This appears to be a missing layer, if I'm understanding my reading correctly. "Optional content" appears to be referencing layers.

I believe so as well. However, she said the pdf wouldn't render in it's original state with all the layers, but I didn't get to try that out to see the error message. She just sent me a version that went through pdfstitcher, so it could be that this error message has nothing to do with the reason why it wasn't rendering. It might just be an artifact from running it through pdfstitcher.
It's hard to troubleshoot pdf issues when patterns usually aren't allowed to be shared. It would be nice to be able to get people to use something like pdf-mangler (made by the creator of pdfstitcher) to make people more comfortable sending pdfs. Asking someone to use a python package seems unrealistic though.

Someone else is having a similar problem with a pattern with large margins: the winnie pants

She just sent me a version that went through pdfstitcher, so it could be that this error message has nothing to do with the reason why it wasn't rendering. It might just be an artifact from running it through pdfstitcher.

This is possible, and based on the fact that is warning and not an error, I'm actually thinking that this isn't the error that caused it to fail. There are many handler hooks on loading, so it's possible that since we haven't implemented all the possible error handlers that we aren't seeing the true cause yet.
Is it putting an error message on the screen? Or is just blank? I'd be happy to try it also, if you think a second pair of eyes would help.

I don't have a copy of the file from the person yesterday because they wanted me to delete it, but the person who reported the issue today mentioned that it was a Made for Mermaids pattern. I checked out their site and they have a lot of free patterns so I downloaded one to test it out. I ran it with PP with all the error checks I could find:
  <Document
      file={file}
      onLoadSuccess={onDocumentLoadSuccess}
      onLoadError={(e) => console.log(e.message)}
      onSourceError={(e) => console.log(e.message)}
    >
      <Page
        pageNumber={pageNumber}
        onGetAnnotationsError={(e) => console.log(e.message)}
        onGetStructTreeError={(e) => console.log(e.message)}
        onGetTextError={(e) => console.log(e.message)}
        onLoadError={(e) => console.log(e.message)}
        onRenderAnnotationLayerError={(e: any) => console.log(e.message)}
        onRenderError={(e) => console.log(e.message)}
        onRenderTextLayerError={(e) => console.log(e.message)}
      />
    </Document>

and none of them were triggered.
So I cloned the pdf.js library and setup their webpack example to see if I could get it to render there and it did. I'm thinking maybe it's time to abandon react-pdf. I've already had to patch it once and as you mentioned in another issue, there's no way to access what we need for layers. What do you think?

I've already had to patch it once and as you mentioned in another issue, there's no way to access what we need for layers. What do you think?

I'm all for using base libraries over wrappers when possible. Wrappers are nice for quick and dirty, but the underlying libraries usually win out in the long run! So, in short, I agree 100%.

So I cloned the pdf.js library and setup their webpack example to see if I could get it to render there and it did.

So, if I'm understanding you correctly, it would not load with react-pdf, but it did load with pdfjs? Interesting

Here's another thing I noticed. The PDFs that are failing for me are showing a little sad face. I don't know if this is what other users are seeing - it's very small, and I couldn't tell what it was until I changed my calibration grid. It looks like it might be a canvas error, like maybe running out memory or something like that:
https://stackoverflow.com/questions/57839322/sad-face-on-canvas-in-chrome

I'm so sorry. I keep missing messages. I'm just seeing all these comments now! It seems like I'm not getting emails from this thread. I was wondering why you never responded and it turns out I was the goofus not responding!
Ok let's try to rip out react-pdf in favour of pdfjs. It was good at getting the MVP out there but it's just causing problems at this point. That being said, my attempt to add pdfjs-dist to the project was disastrous. I tried to follow the webpack example to get access to the worker but even when I got the worker in .next/static/chunks I wasn't able to import it. Are you able to look into adding it to the project? I'll definitely try again but I'm not confident I'll be able to get it working quickly.

No problem - there's a lot of conversations going on right now. I can take a look at it if you want, just know it will probably take me awhile as well, haha.

I got the layers working in the layers branch and tested out a made for mermaids file to see if the custom renderer would fix the issue with the large files opening. The good news is that it will open. The bad news is that the performance is horrible. I think pdfjs still makes more sense. Just thought I’d share. I don’t know much about pin pointing performance issues but I might try to look into it a bit to try to find the issue.

I've been looking into the performance issue/not running with large files and have found that Firefox works for using them in Pattern Projector. A workaround for now!

I've been looking into the performance issue/not running with large files and have found that Firefox works for using them in Pattern Projector. A workaround for now!

This might confirm my suspicion from earlier that browser-dependent maximum canvas size comes into play (could also be maximum file size). Glad to hear it's at least working somewhere.

I was thinking that too, but even if you look at the canvas size maximums in that link you sent, Chrome has way higher maximums than Firefox. I'll keep investigating. Apparently nothing larger than a letter paper pattern will open on IOS, so this seems to be the main thing stopping tablet support right now. My brother-in-law is bringing his extra iPad for me to borrow this weekend so I'll finally have a device to test these issues on!

Oh wow. Thats really interesting 🤔 File handler upload size max maybe? But then you said that pdfjs would open it when react-pdf would not, so maybe not. This one’s tough, for sure.

You were right about this one! pdfjs has a max area for the canvas. The reason why I could open the file with the custom renderer is because the sample custom renderer doesn't scale the viewport based on the devicePixelRatio (like the actual PageCanvas does), so it was much smaller. I found a pdfjs issue for modifying the maxArea where the poster mentioned scaling the canvas up with CSS while keeping the canvas within pdfjs's limits. I put too much into this PR but I got really excited. Pretty please check out the preview whenever you have a chance to see if I missed something! I added a button to recenter the pattern because the patterns are so big!

Hey, I think it's great to get it done! I had not starting looking at it, so I'm happy to let you have this one :)
I hate to show you this, but this is what it did for me when I tried to open a file:
https://github.com/Pattern-Projector/pattern-projector/assets/14338579/d466b029-1c8c-4d9b-9e2b-1bbc38b8b2e1

It is doing the above behavior for any file I open, including the tried and true file I've been using for development.
On the positive side, I could not previously open that file at all, so that's progress!
PS. I think it has something to do with the CustomRenderer. Maybe that class needs to be instantiated in a useMemo or something like that? I'm not 100% sure that's the issue, but I remember running into this before, and I think it started happening when I tried to pass props down to the CustomRenderer. I am using Chrome on a Mac

Ah drat! I knew it was too good to be true. I can’t reproduce the flickering on my computer or phone. So I’ll have to find a way to reproduce the flickering before I can debug it. I’ll definitely check out the prop passing in customrenderer.

That would be awesome! Thank you I’ll try to reproduce and fix it tomorrow midday, but I’ll message if I find a fix. I can’t work on it tonight

Turns out I found time! All I did was convert layers/setLayers into a context provider/consumer instead of passing them through as function parameters. It works beautifully for me now!

OMG! I just did the same thing lol. I couldn't resist either. Brought the laptop into bed.


END event dispatched too early for animation queues

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=437

This issue is being closed as a preparation step before archiving the repository.  See the README for more detail.


ORC-1426: Use Java 21-ea instead of 20 in GitHub Action

What changes were proposed in this pull request?
This PR aims to bump Java 20 GitHub Action job to Java 21-ea.
Why are the changes needed?
To be ready and monitor Java module for Java 21 support later.
Java 21 Early Access Build was released on 2023/5/11.

https://jdk.java.net/21/

How was this patch tested?
Pass the CI.

Could you review this, @williamhyun ?

Thank you always, @williamhyun !

I cherry-picked this test coverage to branch-1.9 too.


Filter by minimum api version

I think it would be a neat feature while looking for a package for slightly older devices :)

Nice idea 💯

Although I have added a filter for minAndroidVersion, but still the process would have to be manual because not many apk variants have multiple supported android versions nowadays. For example YT Music only has 8.0+ for all variants.

A solution for this might be converting that 8.0+ tag to the actual API version and comparing that number to version selected by user. At least I think so 😅. Thank you for such rapid response btw.

Do you mean mapping the android version to the sdk version ? Like Android 15 -> API 35 etc etc. For now i guess the simple logic is best for making the scrapping easier.

Yeah something exactly like that. Simpler logic surely is better especially for scraping, but maybe as the project is entirely in typescript you can add interfaces to make sure the data is scraped correctly and then apply the filters. Just a suggestion to make the project easier to maintain for future features 😉.

Sure, will definitely look into this.


Allow usage of Seccomp Profiles on the restricted PSP

Towards https://github.com/giantswarm/giantswarm/issues/27011

is it properly and fully tested?

Yes, this doesn't change anything more than allowing workloads to use the profiles, it doesn't set a profile. No impact, has been tested.

Any reason not to make it the same as the restricted PSP on vintage (e.g. including the default profile)?

Should we manually apply this change to already existing CAPI clusters? Upgrading a cluster to this version of cluster-shared won't update the PSP's because we are using ClusterResourceSets AFAIK

this is also preventing silence-operator-sync from silence-operator 0.9.0 from running

Should we manually apply this change to already existing CAPI clusters? Upgrading a cluster to this version of cluster-shared won't update the PSP's because we are using ClusterResourceSets AFAIK

should we keep this open @fhielpos @fiunchinho to track which cluster got it applied ?

You can manually annotate the restricted PSP too:
kubectl annotate psp restricted "seccomp.security.alpha.kubernetes.io/allowedProfileNames='*'"

You can manually annotate the restricted PSP too:
kubectl annotate psp restricted "seccomp.security.alpha.kubernetes.io/allowedProfileNames='*'"

Using that command doesn't work
$ kubectl annotate psp restricted "seccomp.security.alpha.kubernetes.io/allowedProfileNames='*'"

Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
The PodSecurityPolicy "restricted" is invalid: metadata.annotations[seccomp.security.alpha.kubernetes.io/allowedProfileNames]: Invalid value: "'*'": must be a valid seccomp profile