merge Taf 8.0 bsf changes to CCB1 branch for testing

What is this and why are we doing it?
incorporate various BSF/ADE related changes for TAF version 8.0

Link to the Jira ticket for this change:

https://jiraent.cms.gov/browse/DBDAART-5716
https://jiraent.cms.gov/browse/DBDAART-5928
https://jiraent.cms.gov/browse/DBDAART-7450
https://jiraent.cms.gov/browse/DBDAART-5931
https://jiraent.cms.gov/browse/DBDAART-5713
https://jiraent.cms.gov/browse/DBDAART-12242
What are the security implications from this change?
none
How did I test this?
testing conducted in VAL via several notebooks, subject to internal team review
Should there be new or updated documentation for this change? (Be specific.)
updates to documentation (specs, requirements, and layouts) has been handled elsewhere
PR Checklist

[x] The JIRA ticket number and a short description is in the subject line
[ ] My code follows any applicable style guides
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Thanks Ali, do you need to merge from CCB1 into this branch first?   I have changes on CCB1 that I do not see in TAF 8.0 BSF branch.

Hey @a-pfeiffer, there were no overlapping file changes between CCB1 and this branch. But, your recommendation is a good one, and I have made that pr and merge. TAF 8.0 BSF is now up to date with CCB1. You should be good to go with your review. Please let me know if you have any other issues. Thanks,

@fumanjie @alihashmi-wh
Mathematica has approved both of these pull requests. Please complete the pull and delete the source branch. However, please take care that one pull request does not unintentionally overwrite/undo changes from the otehr.
cc @alihashmi-wh @XiaoBarry


Replace #sizeWordStack(_, _) helper with direct recursion

The change is only applied to the symbolic backends; the tail-recursive helper
is retained for concrete backends. The change allows using the memo attribute
with the Haskell backend, reducing runtime of the sum-to-n spec by over 50%. We
are also able to remove lemmas from several specs.

This is okay, I suppose, but I'd be happier with a solution that just made computing the size be constant time instead.

I'd be happier with a solution that just made computing the size be constant time instead.

After discussion with @ehildenb this morning, we don't think there is a way to do that in the semantics.

I would have to coordinate changes to verified-smart-contracts to make this change, and I don't want to do that. However, we can probably achieve the same effect by applying memo elsewhere.


Fix padding factoring in IncidentCard

Who is this PR for?
educators
What problem does this PR fix?
Follow-on to fix styling bug from refactoring in https://github.com/studentinsights/studentinsights/pull/1492.
What does this PR do?
Fixes refactoring bug; I missed this with just one incident but it's quite visible in production with more than one incident :)
Screenshot (if adding a client-side feature)
(avoiding screenshotting any data, you can see the vertical margin)

Checklists
Javascript QA

[x] Author checked latest in IE - Student Profile

selfie


How do I disabled dates from now to future?

How do I disabled dates from now to future? I mean for example if I'm using the component on a birthday field then I can not born on 2020 or something like that, how I disable future dates?

You should work with the enddate option. Use currentdate as the end date to disabled dates in the future


[hotfix] Update Active Metaschemas [OSF-8641]

Purpose

There are several metaschemas in the DB that are incorrectly marked as active. This migration will make inactive all metaschemas that are not version 2 and listed in ACTIVE_METASCHEMAS.

Ticket

OSF-8641

Actually, just thought a case where the migration might not do the right thing: If a new schema is added and a developer sets up a fresh database/dev environment then run the migration, the new schema will be marked as inactive.
Therefore, the migration should probably just be:
MetaSchema.objects.filter(schema_version__lt=2).update(active=False)


Typography fixes

https://github.com/cds-snc/cra-claim-tax-benefits/issues/468
Addresses the 3 major issues from the linked issue:

Question text / hint text length has been made longer
Full width paragraphs have been shortened to match the start and confirmation pages
Titles will wrap to a second line earlier, reducing the max-width of the title.

@brdunfield, almost there. Sorry for being really picky but 2 things 🙏

We can skip the header padding on small screens since it's only on large screens we see the super long line lengths.

before
after

header text has no padding (looks okay on a small screen)
header text has a padding (let's skip it)

Inputs: let's keep 'em the same max width as they are on the current "live" service. (I know when you shrink the screen they get smaller — that's okay)

Here's a gif that shows them going back and forth. (The longer inputs are the new CSS.)

So yeah, let's max them out at the current "live" size.


Feature Request: script modifier / rewrite properties

As described here, in structural replace it is possible to apply small script modifiers to values. For example, Field.name.toLowerCase() turns the matched value into lower-case and then replaces it.

It would be nice if this was possible in ssr.nvim with lua scripts or to have something like Comby's rewrite properties.

This would definitely be a great enhancement! However adding a bunch of text editing properties  is very limited, you can only use a predefined set of simple functions. And use full power of Lua scripting is an overkill.
I want to make ssr.nvim can call vim’s built commands, so I can use gu for toLowerCase. I also want to call commands from plugins, so I can use dial.nvim to change text cases and use treesj or ts-node-action to make structural edits. I can use the same technique I’m already familiar with.
Lastly, I’m thinking about a “structural macro recording” feature, where ssr.nvim translates macro into search-replace. Making ssr.nvim uses vim commands instead of predefined properties or Lua scripts also fits well in this situation.
(Just some thoughts, I don’t think I have energy to implement anything recently 😢)

If I understand correctly you'd want something like an enhanced macro that records keypresses/commands on tree-sitter nodes and replays those on every structural edit?
Maybe an example (in Python, but doesn't really matter):
one = (1, "one")
two = (2, "two")

I want to switch the position of two values in a tuple and at the same time make the variable name uppercase.
With Comby-like rewrite properties I can imagine something like this
SEARCH:
$var = ($num, $str)
REPLACE:
$var.UPPERCASE = ($str, $num)

How would the macro approach look like for the same? Where/when would I record the macro? I am not sure it would be easy to capture what is a structural edit and what is a regular edit?

wrote a PR for using lua expressions in the REPLACE field #39
I wrote it before reading the discussion here, but I just want to leave some thoughts here.

integration with multicursor plugins might be more in line with what cshuaimin suggested.

while lua is probably overkill, it's familiar to the user and makes it easier for users to extend this functionality with their own scripts


[AST] Move storage of same-type-to-concrete constraints to EquivalenceClass.

Most clients that will be considering same-type-to-concrete
constraints will need to look at all of the constraints within the
equivalence class together. Store the same-type-to-concrete
constraints on the EquivalenceClass itself, which fits this use case
better, and should reduce the storage requirements by making potential
archetypes two pointers smaller. NFC

@swift-ci please smoke test and merge


Weird white space at the bottom of a screen in the feedback flow

Open a service detail
Click suggest an update
Change name or other details
Enter some feedback
Click Submit
Fill in an email
Check the "Do you work at this service or organization?"
Scroll all the way down the page (the keyboard overlay will be visible at this point)
Observe that there is a lot of empty white space at the bottom of the page
Expected is that there will be only a small amount of white space below "Job Title" field
Note that this issue may be platform dependent, related to how the keyboard overlay works on the two platforms
Acceptance Criteria

[ ]  The extra white space is gone, looks correct on both platforms

This is to make the keyboard not obscure the bottom of the field on Android


backbutton to exit app(cordova), how to do this?

phonon.js handles backbutton event in cordova, this prevents the default cordova behavior: press back button in the home page to exit the app.
How should we bring back this? Thanks a lot!

You can use something like this https://gist.github.com/John-Henrique/b7ecd97147604438356d

Thanks! So how can I know the current page is the entry? For normal navigation after the entry, I think the back button should go back, when there is no previous page, it should exit.

Please read Docs, it's interesting Phonon Navigator

@txchen : I changed the behavior of the backbutton.
I will add this patch in the release 1.2.0 (coming asap).
(https://github.com/quark-dev/Phonon-Framework/releases)[https://github.com/quark-dev/Phonon-Framework/releases]


Fails w/ SSR pages

When running on a project with an SSR page (there is no GraphQL query on that page), I see this error:
"gatsby-plugin-perf-budgets" threw an error while running the onPostBuild lifecycle:

ENOENT: no such file or directory, open /usr/src/app/www/public/page-data/ssr-profile/page-data.json

166 |     const pageDataStatsPath = getFilePath({ publicDir }, pagePath);
  167 |
> 168 |     const content = fs.readFileSync(pageDataStatsPath, `utf-8`);
      |                        ^
  169 |
  170 |     const parsedContent = JSON.parse(content);

Not sure if those pages should just be ignored or not.

I added a GraphQL query to the same page, but it still failed.  So likely these SSR pages should just be ignored for now?

Also fails when page generation is deferred using defer: true option in createPage


improve some text info inside src/scripts/createdb.js

Describe the bug
Improve the following inside src/scripts/createdb.js
export default User.drop(() => {
  console.log('Successfully dropped db')
}).catch(error => {
  console.log('The Error', error)
})

To Reproduce
Expected behavior
export default User.drop(() => {
  console.log('Successfully dropped user table')
}).catch(error => {
  console.log('The Error', error)
})

Screenshots
Desktop (please complete the following information):

N/A

Smartphone (please complete the following information):
-N/A
Additional context
N/A

It also needs to make a modification to allow more than one export. In an app, it can have many tables.

Since this is creating tables, we can run the function rather than exporting it.
The command to create tables is npm run create:db.
Also, with such naming, naming change is required to be create-tables.js instead of createdb.js.


Proper refs for TextField and ref typing

[x] TextField refs can properly access TextFieldInput
[ ] All Elements that are wrappers around an <input> element allow access to a reference of that input element
[ ] Type all refs

A ref of TextFieldInput can be accessed via
text_field_ref.tfInput

Input refs will be accessible via
ref.input

What's are we trying to achieve with this?

All Elements that are wrappers around an  element allow access to a reference of that input element

I would discourage this. The underlying Dom is not for us to own. A ref to this would make a breaking change for us even though mdc APIs remain same

A ref to this would make a breaking change for us even though mdc APIs remain same

Where do you see a breaking change?

The underlying Dom is not for us to own

Is't pure preact

What's are we trying to achieve with this?

Currently the only way to access the input element (see #702, e.g. for calling DOM methods on it) is either to use MDComponent._input (what's definitely discouraged) or traversing the DOM your self (using document.getElementById() etc.; that's also discouraged, because as you said, the DOM is not owned by us).

Example for a DOM API not supported by MDCComponents: reportValidity()

Where do you see a breaking change?

E.g. Select was never implemented using the  component until recently, if someday they go back it won't be a breaking change for them as the APIs will be same but it will be for us as we won't have a Dom to give ref to.
Therefore I would suggest to own only mdc properties and not have any additional logic on us.
Plus a Dom ref to top level always exposes inner Dom to work with.

Traversing through the inner Dom is really manual, there are use cases that need that Dom ref, so the alternative is to tell the users to use some hacks to that will also have that breaking changes and are not designed to be used like this. That means that this would be a breaking change from MWC which we cannot influence any ways.
Maybe would do better to implement that and then mark it as "Only use it, if you really need"

Maybe would do better to implement that and then mark it as "Only use it, if you really need"

I've had some discussion to add some kind of "experimental"  features to this package always. Just never had enough time to do so.
Do u have a good API design to do so?

Do u have a good API design to do so?

The only thing I can think of right now is annotating it in the docs and annotating it in the source.

Dopping this in favor of the refactor for 2.0

Please leave the branch for now


feat: mTLS support

Change-Id: I90f61317b47062cffff6af0c92db7feff2232aa4
Fixes for #65

This is very out-of-date and should be fixed now. I'm going to close this. There's a nice feature, though, around creating the list of user certificates that I've added an issue (#775) for.


French translation

EDIT: Oh well, someone already made a french translation -_- I didn’t saw it I suppose. According to his work on Minetest' localization, you should pull his request, not mine.

Oh well, someone already made a french translation

@etnadji sorry about the duplicate work :/ If you want you can help reviewing https://github.com/MrS0m30n3/youtube-dl-gui/pull/203 and/or send patches on top of @fat115's pull request (this branch).
If you're ok with that I will close this PR now to avoid confusion. Thanks for your work


Ability to use different ip address for ibgp peering in non default vrf

Enhancement summary
AVD today defaults to using mlag_peer_l3_ipv4_pool to create the bgp peering.
In the vxlan EVPN environment, ibgp peering created over the SVI in a non default vrf requires the ability to use different ip address across different vrfs.
Which component of AVD is impacted
eos_designs
Use case example
VXLAN evpn deployment which is acting as aggregation for the different routes for running the overlay SDWAN solution.
Although reusing the ip addressing across different vrfs should work, customer prefers to use different ip addressing for the ibgp peering vlans.
Describe the solution you would like

SVI creation with custom ip pool
iBGP Peering configured using the ip address in the /31 subnet assigned to the SVI created in step 1
IBGP peer activation in address family IPv4 for that non default vrf where ibgp peering is created
Ability to assign it to different peer group (by default ibgp peer is getting assigned to peer group MLAG-IPv4-UNDERLAY-PEER)

Describe alternatives you have considered
Nothing found yet.
Additional context
No response
Contributing Guide

[X] I agree to follow this project's Code of Conduct

Currently the SVI creation for non default vrf to use different ip address is being done using custom_structured_configuration_vlan_interfaces

Could be addressed with a new mlag_ibgp_peering_ipv4_pool under tenants.<>.vrfs.<> to be consistent with the var naming in that context.


Is it possible to modify the window controls?

Hi there, I've been looking at yours theme and the Darcula theme, https://github.com/alecGraves/WolframNotebookDarculaTheme, and I wonder whether you can also modify the colors of the windows.
It seems that the author of https://gitlab.com/jakobneef/mathemeatica did it, but I don't really know how, so I'm letting you know of that and maybe you could find a way of extending your theme to the window controls!

@jpmvferreira do you mean like the application window? i'm not sure. from the links you sent, it looks like their computer desktop file bar is matched to the theme, so it's probably something that's controlled by the OS. but if you find out anything else please feel free to let me know 😄

Before I forget, once I have the time to dig into this, it would also be nice if we have the power to change the menu bars to hide specific elements.
I'm not quite sure how easy it is to do this, I've send about 10 minutes figuring out how to hide the bottom horizontal bar that shows the zoom level and failed, so if this feature we can manipulate things at a lower level than that what is offered to the end user then that could also be an option.


[fpv] prim and top-level IP improvements

Description
For Earlgrey-PROD.M4 and as part of #22721  @rswarbrick managed to substantially improve FPV pass rates and coverage for the prim and top-level IP regressions:

https://reports.opentitan.org/hw/top_earlgrey/formal/ip/summary/latest/report.html
https://reports.opentitan.org/hw/top_earlgrey/formal/prim/summary/latest/report.html

As documented by @rswarbrick here, the following two things remain to be resolved for future releases:

Improving pass rates for prim_fifo_sync_fpv and prim_fifo_async_sram_adapter_fpv. These might need some tooling workarounds.
Improving coverage numbers for pinmux and rv_plic. Most existing gaps are due to COIs of SVAs not touching the signals of interest, in particular inside u_reg.

Both these items are of lower priority but if we decide to investigate this further, this issue can serve as a starting point / reference to previous work.

The pass rates described as the first item here should get to 100% with the changes in #24432 and #24433.


Performance plugins

Added two performance-related linting plugins

Ooo, these are cool. Do you mind fixing linting issues? Happy to merge these afterwards.

Ah, apologies--Amended. I also added a commit if you're ok with it--to have an .editorconfig, especially helpful in such cases when there is no .eslintrc.* file to get the enforced code (though I know I should have checked that).

Thank you! That's a great addition - good catch.

Cool--and thanks for the repo access. A very useful collection to have all in one place!


Validation issue with<PHONE_NUMBER> (IL)

See here.
Please read the "guidelines for contributing" (linked above) and fill in the template below.
Country/region affected (e.g., "US"): IL
Example number(s) affected ("+1<PHONE_NUMBER>"):<PHONE_NUMBER>
The phone number range(s) to which the issue applies ("+1 555 555-XXXX"):
The type of the number(s) ("fixed-line", "mobile", "short code", etc.):
The cost, if applicable ("toll-free", "premium rate", "shared cost"):
Supporting evidence (for example, national numbering plan, announcement from mobile carrier, news article): IMPORTANT - anything posted here is made public. Read the guidelines first!
link to demo

Hi,
Thank you for taking the time to improve libphonenumber!
We can't connect to +972 556117772. Did you have a typo?
We found evidence that 5561XXXXX is valid.
We've accepted this issue and will fix this in an upcoming release.
Please note that you have submitted this information with the knowledge that we may use, modify, reproduce, publicly display, and distribute the information in accordance with our open source policies. Please let us know if you did not intend to submit the information for such use.

Hi,
We can't connect to +972 556117772. Could you please share any other working number?
The wiki link provided by you is very generic and lenient. Sorry the evidence we found earlier is also very generic. We follow ITU document to do the updates as it is more accurate. We could not find any working numbers online so we cannot support 5561xxxxx unless we get evidence.
Please share any working numbers or official evidence you may have. See our guidelines.

Hi,
This issue is blocked on your or other GitHub contributors' input. Please help us find evidence that 5561 is valid, or provide an example number from a business website or similar. Otherwise we don't have enough information to fix the issue and may have to close it as infeasible.

I'm closing as this issue is infeasible for us to fix at this point (we need more information). Please re-open if you respond so we pick up on it.

Thanks. This was a bug that was reported to us by one of our customers. We've told them to give us a working phone number with this prefix, but they haven't responded. We will re-open if they ever respond.


9 digits in Brazil

In Brazil there are phones with up to 9 digits. Is it possible to include this in the validation of the number?
Tnx

The selector is relying on google liphoneutils, so if the google lib has
been updated to take them into account, it should work, you can replace the
lib files
On Thu, May 25, 2017 at 5:19 AM Gustavo Meredyk<EMAIL_ADDRESS>wrote:

In Brazil there are phones with up to 9 digits. Is it possible to include
this in the validation of the number?
Tnx
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pierre-vigier/intlpnIonic/issues/22, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AHMnhWZlQBJJCT-SlonsGi7zGnMxGFNJks5r9J7igaJpZM4Nlrtw
.

i just released version 0.1.10 with an updated version of the number utils. It's now working with Brazilian 9 digits mobile phones


[DNM]Enable the resgroup test cases

fix #ISSUE_Number

Change logs
Describe your change clearly, including what problem is being solved or what feature is being added.
If it has some breaking backward or forward compatibility, please clary.
Why are the changes needed?
Describe why the changes are necessary.
Does this PR introduce any user-facing change?
If yes, please clarify the previous behavior and the change this PR proposes.
How was this patch tested?
Please detail how the changes were tested, including manual tests and any relevant unit or integration tests.
Contributor's Checklist
Here are some reminders and checklists before/when submitting your pull request, please check them:

[ ] Make sure your Pull Request has a clear title and commit message. You can take git-commit template as a reference.
[ ] Sign the Contributor License Agreement as prompted for your first-time contribution(One-time setup).
[ ] Learn the coding contribution guide, including our code conventions, workflow and more.
[ ] List your communication in the GitHub Issues or Discussions (if has or needed).
[ ] Document changes.
[ ] Add tests for the change
[ ] Pass make installcheck
[ ] Pass make -C src/test installcheck-cbdb-parallel
[ ] Feel free to request cloudberrydb/dev team for review and approval when your PR is ready🥳

will rebase this pr after https://github.com/cloudberrydb/cloudberrydb/pull/531

no sure why no exec the prepare_resgroup, let me check

FYI: I also added this new icw-resgroup-test as one required check for the pull request merge.


Sign messages, add permissioned order operation for delete

Fixes #117
Fixes #115

+1 after you run make protoc :shipit:


Added PDB header service

Moved over the PDB info service implementation, with a simple key-value pair caching, from the https://github.com/genome-nexus/g2s/tree/master/pdb module, so that we can retire pdb-annotation.war.

Codecov Report

Merging #83 into master will decrease coverage by 4.72%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master      #83      +/-   ##
============================================
- Coverage     29.14%   24.42%   -4.73%
  Complexity       37       37
============================================
  Files            26       28       +2
  Lines           470      561      +91
  Branches         62       83      +21
============================================
  Hits            137      137
- Misses          320      411      +91
  Partials         13       13

Impacted Files
Coverage Δ
Complexity Δ

...l/genome_nexus/service/internal/PdbFileParser.java
0% <0%> (ø)
0 <0> (?)

...ome_nexus/service/internal/PdbDataServiceImpl.java
0% <0%> (ø)
0 <0> (?)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 722d52b...9d7bd0e. Read the comment docs.


wip 2.4 branch incompatible with 2.4-M3 akka

Caused by a commit:
https://github.com/akka/akka/commit/c5851600f0e1025dda3877fa934a852ab2020925

Configuration property akka.persistence.journal.max-message-batch-size has been moved into the plugin configuration
+section, to allow different values for different journal plugins

Haven't integrated with M3 yet, I will look at this week.

Updated it locally. Happy to put up a PR for this, if interested.
Assumption made: max-message-batch-size works for both bach writes and batch deletes (following what they did in the akka codebase)

I am not a maintainer but go for it I would like to compare with my solution :)

Can we close this ticket (after the recent merge to wip-akka-2.4)?

Yes we're 1 release after M3 now.


Clients without the mod can't join when opening to LAN

Title. Vanilla clients can join fine; only clients with Fabric API but without Particle Rain fail to connect, getting a "Received 7 registry entries that are unknown to this client." message instead.

relevant part of log
[10:32:04] [Render thread/ERROR]: Received unknown remote registry entries from server
[10:32:04] [Render thread/ERROR]: Registry entry (particlerain:rain_drop) is missing from local registry (minecraft:particle_type)
[10:32:04] [Render thread/ERROR]: Registry entry (particlerain:snow_flake) is missing from local registry (minecraft:particle_type)
[10:32:04] [Render thread/ERROR]: Registry entry (particlerain:desert_dust) is missing from local registry (minecraft:particle_type)
[10:32:04] [Render thread/ERROR]: Registry entry (particlerain:weather.snow) is missing from local registry (minecraft:sound_event)
[10:32:04] [Render thread/ERROR]: Registry entry (particlerain:weather.snow.above) is missing from local registry (minecraft:sound_event)
[10:32:04] [Render thread/ERROR]: Registry entry (particlerain:weather.sandstorm) is missing from local registry (minecraft:sound_event)
[10:32:04] [Render thread/ERROR]: Registry entry (particlerain:weather.sandstorm.above) is missing from local registry (minecraft:sound_event)
[10:32:04] [Render thread/ERROR]: Registry remapping failed!
java.util.concurrent.CompletionException: net.fabricmc.fabric.impl.registry.sync.RemapException: Received 7 registry entries that are unknown to this client.
This is usually caused by a mismatched mod set between the client and server. See the client logs for more details.
The following registry entry namespaces may be related:

particlerain

	at net.fabricmc.fabric.impl.registry.sync.RegistrySyncManager.lambda$receivePacket$0(RegistrySyncManager.java:146) ~[fabric-registry-sync-v0-4.0.18+78d798af4f-4d8236a4789003c6.jar:?]
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768) ~[?:?]
	at net.minecraft.class_1255.method_18859(class_1255.java:156) ~[client-intermediary.jar:?]
	at net.minecraft.class_4093.method_18859(class_4093.java:23) ~[client-intermediary.jar:?]
	at net.minecraft.class_1255.method_16075(class_1255.java:130) ~[client-intermediary.jar:?]
	at net.minecraft.class_1255.method_5383(class_1255.java:115) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.method_1523(class_310.java:1283) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.method_1514(class_310.java:888) ~[client-intermediary.jar:?]
	at net.minecraft.client.main.Main.main(Main.java:265) ~[minecraft-1.20.4-client.jar:?]
	at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:470) ~[fabric-loader-0.15.7.jar:?]
	at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74) ~[fabric-loader-0.15.7.jar:?]
	at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23) ~[fabric-loader-0.15.7.jar:?]
	at org.prismlauncher.launcher.impl.StandardLauncher.launch(StandardLauncher.java:87) ~[NewLaunch.jar:?]
	at org.prismlauncher.EntryPoint.listen(EntryPoint.java:130) ~[NewLaunch.jar:?]
	at org.prismlauncher.EntryPoint.main(EntryPoint.java:70) ~[NewLaunch.jar:?]
Caused by: net.fabricmc.fabric.impl.registry.sync.RemapException: Received 7 registry entries that are unknown to this client.
This is usually caused by a mismatched mod set between the client and server. See the client logs for more details.
The following registry entry namespaces may be related:

particlerain

	at net.fabricmc.fabric.impl.registry.sync.RegistrySyncManager.checkRemoteRemap(RegistrySyncManager.java:365) ~[fabric-registry-sync-v0-4.0.18+78d798af4f-4d8236a4789003c6.jar:?]
	at net.fabricmc.fabric.impl.registry.sync.RegistrySyncManager.apply(RegistrySyncManager.java:261) ~[fabric-registry-sync-v0-4.0.18+78d798af4f-4d8236a4789003c6.jar:?]
	at net.fabricmc.fabric.impl.registry.sync.RegistrySyncManager.lambda$receivePacket$0(RegistrySyncManager.java:143) ~[fabric-registry-sync-v0-4.0.18+78d798af4f-4d8236a4789003c6.jar:?]
	... 14 more
[10:32:04] [Render thread/WARN]: Client disconnected with reason: Received 7 registry entries that are unknown to this client.
This is usually caused by a mismatched mod set between the client and server. See the client logs for more details.
The following registry entry namespaces may be related:

particlerain

This was with version 2.0.8 of the mod.

I tried preventing the registry sync but particles that get spawned on the server player's world seem to get sent to the other players for some reason, causing them to lose connection. I don't know if fabric api causes this or if vanilla does it too and just fails silently.
This is too niche of an edge case for me to consider spending more time on, sorry.

Is this helpful? https://github.com/ViaVersion/ViaFabricPlus/commit/8c34100ee15976b77cba05093ec6aa841e74ad24
If not, I appreciate that you tried. I've been reporting similar problems with other mods, and some maintainers have been rather dismissive.

The registry wasn't a problem when I bypassed it. The issue now is that the server world and client world seem to become the same thing on LANs, so its sending the spawn packet to the other clients and they can't decode it likely because they don't have those particles registered. I might have another look later but I'm hesitant to dedicate much time to quite specific edge cases.

The spawn packet issue not making any sense was annoying me enough to want to track down the cause, and boy do I feel silly now. Particles spawned by command use the spawn packet and I had forgotten about the command block I had in my test world. It otherwise has been working fine this whole time. Thanks for linking to ViaFabricPlus. I figured out a similar approach instead of just disabling the sync.


Requests hang forever when using integers as values in multipart

Environment
uname -a output:
Linux hostname-pc 4.17.3-100.fc27.x86_64 #1 SMP Tue Jun 26 14:19:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

elixir --version output:
Erlang/OTP 20 [erts-9.2] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:10] [hipe] [kernel-poll:false]

Elixir 1.6.2 (compiled with OTP 19)

Current behavior
When passing a integer value as third argument to add_field/4, it never returns when executing the request:
alias Tesla.Multipart
chat_id_int = -1_001_143_002_998
token = Application.get_env(:tg, :token)

mp =
  Multipart.new()
  |> Multipart.add_field("chat_id", chat_id_int)
  |> Multipart.add_file("test.txt", name: "document")

Tesla.post("https://api.telegram.org/bot#{token}/sendDocument", mp) # Hangs forever

This works fine:
alias Tesla.Multipart
chat_id_str = "-1001143002998"
token = Application.get_env(:tg, :token)

mp =
  Multipart.new()
  |> Multipart.add_field("chat_id", chat_id_str)
  |> Multipart.add_file("test.txt", name: "document")

Tesla.post("https://api.telegram.org/bot#{token}/sendDocument", mp)

Expected behavior
I would expect it to either work fine with integers or to throw an error when I try to pass something that is not a string, whichever makes more sense.

I can't test this right now, please try to produce the failing minimal example against requestbin or similar service.

Using string:
mp =
  Multipart.new()
  |> Multipart.add_field("foo", "123")

Tesla.post("http://requestbin.net/r/1mw0e3c1", mp)

Output:
{:ok,
 %Tesla.Env{
   __client__: %Tesla.Client{fun: nil, post: [], pre: []},
   __module__: Tesla,
   body: "ip:<IP_ADDRESS>\n",
   headers: [
     {"connection", "keep-alive"},
     {"date", "Wed, 18 Jul 2018 20:22:07 GMT"},
     {"via", "1.1 vegur"},
     {"server", "cloudflare"},
     {"content-length", "18"},
     {"content-type", "text/html; charset=utf-8"},
     {"set-cookie",
      "__cfduid=d0511378e77d3b91c1043de753a3482371531945327; expires=Thu, 18-Jul-19 20:22:07 GMT; path=/; domain=.requestbin.net; HttpOnly"},
     {"sponsored-by", "http://requestbin.net"},
     {"cf-ray", "43c7a897729ab8b9-MIA"}
   ],
   method: :post,
   opts: [],
   query: [],
   status: 200,
   url: "http://requestbin.net/r/1mw0e3c1"
 }}

Using integer:
mp =
  Multipart.new()
  |> Multipart.add_field("foo", 123)

Tesla.post("http://requestbin.net/r/1mw0e3c1", mp)

Never outputs.

The hanging part is because of httpc (the default adapter). However, the body should be an Enumerable. When it's binary it's converted to [body] by tesla.
The error is much more clear when used with hackney adapter:
** (Protocol.UndefinedError) protocol Enumerable not implemented for 123. This protocol is implemented for: Date.Range, File.Stream, Function, GenEvent.Stream, HashDict, HashSet, IO.Stream, List, Map, MapSet, Range, Stream
    (elixir) /home/ubuntu/bob/tmp/e00399d85b8d200de0c17f19231c78a9/elixir/lib/elixir/lib/enum.ex:1: Enumerable.impl_for!/1
    (elixir) /home/ubuntu/bob/tmp/e00399d85b8d200de0c17f19231c78a9/elixir/lib/elixir/lib/enum.ex:141: Enumerable.reduce/3
    (elixir) lib/stream.ex:923: Stream.do_enum_transform/7
    (elixir) lib/enum.ex:1919: Enum.reduce/3
    (tesla) lib/tesla/adapter/hackney.ex:74: Tesla.Adapter.Hackney.request_stream/5
    (tesla) lib/tesla/adapter/hackney.ex:31: Tesla.Adapter.Hackney.call/2

I think we need to add a guard to Multipart.add_field/3 to prevent passing unsupported data.


Unified Service Desk 4.1 - Dynamics 365 - Automation Help

We have to do test automation in Unified Service Desk 4.1 Dynamics 365.  Can we use WinAppDriver and Appium for test automation?
@timotiusmargo @paulcam206 @hassanuz @yodurr

Hey just as a heads up - I'm not sure that anyone you tagged is actually a member of the WinAppDriver project 😄
I know that @timotiusmargo is but I don't know who the PM is anymore.

You can check using inspect.exe , if you get the elements in inspect, you are good to go.

@jjbright Yes, it possible.
I used WinAppDriver for USD automation.
You just need to turn on accessibility support

Hi @jjbright,
I tried to automate USD 4 using UFT and problem started at case classification fields once after new case is clicked and could not move any further. Please let me know if you find any solution and how you are automating this USD 4. Thanks in advance!

other API's are used, closed #1127

@jjbright What API are you going to use?


Codesign the app

See: https://www.electron.build/code-signing
We can set it up in Travis, but we need certificates for macOS (easy) and Windows (hard).
The priority is getting macOS codesigning set up as it currently makes it difficult to open the app without. (The 0.1.0 milestone is for macOS only)

[x] macOS
[ ] Windows

What's the drawback of not codesigning with Windows?

@lukechilds I don't think it's worth the effort to codesign on Windows: https://github.com/ImageOptim/gifski/releases/tag/0.8.3

Wow. Yeah, lets not do that.
No Windows testers have even mentioned issues about signing anyway. (AFAIK)


INFO: Build completed, 1 test FAILED, 2648 total actions
//test/cpp/end2end:cfstream_test                                         FAILED in 30.6s

How can I know when this is safe to re land?

I suggest testing your branch with go/grpc-local-testing and spawning an ephemeral kokoro job to do adhoc testing

Basically running something like run_adhoc_kokoro_job.py --original_job grpc/core/master/macos/grpc_cfstream.cfg --branch your_branch --repo ctiller/grpc (see internal docs for more details) should do the job.


improve responsive columns on developer view. fixes #330

I have asked for clarification on exactly what #330 is trying to fix.

I think it has something to do with the 'dry' reflow when the breakpoint is reached. I made it smoother. The columns now grow fluidly.


Cannot install Jupyter C# kernel with the provided dockerfile - error Microsoft.PowerShell.Native not found

Describe the bug
I'm trying to run my own jupyter notebook using MyBinder. I have copied your dockerfile and nuget.config over into my repo and am trying to start the container with mybinder. The installation progresses up until the point where the jupyter kernel gets installed, and then I get the following error message:
Error:
An assembly specified in the application dependencies manifest (Microsoft.DotNet.Interactive.App.deps.json) was not found:
package: 'Microsoft.PowerShell.Native', version: '7.0.0-rc.1'
path: 'runtimes/linux-x64/native/libmi.so'
My mybinder url is: https://mybinder.org/v2/gh/mdfarragher/GLC0220/master?filepath=%2Fblob%2Fmaster%2FRegression%2FTaxiFarePrediction%2FTaxiFarePrediction.ipynb
And my repo is here: https://github.com/mdfarragher/GLC0220
Did this error occur while using dotnet interactive?

[x] .NET Jupyter Notebook

Screenshots

Please complete the following:

OS

[X] Windows 10
[ ] macOS
[ ] Linux (Please specify distro)
[ ] iOS
[ ] Android

Browser

[ ] Chrome
[X] Edge (the new one)
[ ] Safari

@brettfo

The issue is that two identical* packages were published to MyGet and MyGet handles this by overwriting the package.  The 'identical' package was really a symbols package *.symbols.nupkg that was specially created for internal symbol archiving purposes, but due to a limitation in the tool, two binaries had to be stripped out; libmi.so and libpsl-native.so.
I've created PR #113 that publishes to MyGet using a build artifact that doesn't have the symbols packages, so we won't run into the overwrite problem.  Once that PR has merged, an internal signed build will be automatically started which will push new (and correct) packages to MyGet.  ETA less than 1 hour from this comment.

tl;dr - The MyGet packages have been fixed.  Try to re-generate your MyBinder image and as long as the version of dotnet-interactive that's installed is 1.0.110308 or greater, it should work.
The latest package is up on MyGet and I was able to verify it's behavior by running the following under Ubuntu:
dotnet tool install -g Microsoft.dotnet-interactive --add-source "https://dotnet.myget.org/F/dotnet-try/api/v3/index.json"

Tool 'microsoft.dotnet-interactive' (version '1.0.110308') was successfully installed.
I was then able to force execution of a simple PowerShell command with the following:
dotnet interactive kernel-server
Paste in this:
{"token":"abc","commandType":"SubmitCode","command":{"code":"1+1","submissionType":0,"targetKernelName":"powershell"}}
And in the output spew, saw that the value 2 was computed.  I could also re-try the console submission but with "targetKernelName":null to default to C# and it also did the appropriate thing.

Note, until mybinder clears their docker cache, this will still fail to build with the default Dockerfile.  You'll be able to tell because the log under the line RUN dotnet tool install ... you'll see ---> Using cache.  You should be able to work around this by adding --version 1.0.110308 to the install line.

Looks like the mybinder cache has been updated, so it should work now.

I can confirm it's fixed. I just added the version flag to my dockerfile and everything works perfectly now. Thanks for the fix @brettfo!


Traslate to English?

I will be translated into English in the future，thank you

is it has done? where's the translation?


[WIP] added cli options for declined offers

Looking for feedback for the CLI code, tests will follow. Here some examples:
$ dcos marathon launchqueue list
ID        SINCE                     INSTANCES TO LAUNCH  OVERDUE  PROCESSED OFFERS  UNUSED OFFERS  LAST UNUSED OFFER         LAST USED OFFER
/sleeper  2016-11-14T09:57:09.315Z  9                    True     66                65             2016-11-14T12:22:28.555Z  2016-11-14T09:57:09.496Z

$ dcos marathon launchqueue summary /sleeper
RESOURCE     REQUESTED                 DECLINED  DECLINED PERCENTAGE
CONSTRAINTS  [['hostname', 'UNIQUE']]  33 / 34   97.06%
ROLE         *                         32 / 66   48.48%
PORTS        [10000]                   0 / 1     0.00%
MEM          128                       0 / 1     0.00%
GPUS         0                         0 / 1     0.00%
DISK         0                         0 / 1     0.00%
CPUS         1                         0 / 1     0.00%

$ dcos marathon launchqueue details /sleeper
HOSTNAME    REASON                                                 RECEIVED
<IP_ADDRESS>   UnfulfilledConstraint                                  2016-11-14T12:22:28.555Z
<IP_ADDRESS>  InsufficientCpus, InsufficientMemory, UnfulfilledRole  2016-11-14T12:22:28.555Z

I like the summary view, that's perfect.
The detail view feels like it should be a table akin to the UI.
How about making the command debug instead of launchqueue to match the UI.
I'd like to see something in dcos marathon app list instead of buried under a different command. Probably only needs to be similar to what we're doing in the UI (warning column with yes/no).

Thanks for the feedback @pyronicide !
2.) The full table with crosses and checks?
3.) What exactly are you suggesting?
dcos marathon debug list
dcos marathon debug summary <app-id>
dcos marathon debug details <app-id>

4.) I would add a column with the hint like stuck or something similar. We do have this for PODs as well..

Yup, it seems like a good idea .... tell me what you think.
Sounds good to me.
👍

@pyronicide updated the PR related to your feedback and updated the description. Does this behavior matches your requirements?

Enhancements of marathon app list and marathon pod list will follow

Couple things missing that came up during the conversation from the UI:

Resources aren't funneling (0/1 all the way down).
I don't have the total offers for summary or detail view. I'd love to see a count there.
GPUs are still there =)

1.) dcos marathon debug summar is ordered by declined percentage descending. The idea was to display the most revelvant reasons at the top.  In that example 66? Suggestions where to put this?
3.) ok ok, got it that you don`t want to see gpus =)

I like the ordering, and the declining percentages. Unfortunately, it is 50/50 right now. I would expect something closer to this:

$ dcos marathon debug summary /sleeper
RESOURCE     REQUESTED                 DECLINED  DECLINED PERCENTAGE
CONSTRAINTS  [['hostname', 'UNIQUE']]  33 / 34   97.06%
ROLE         *                         32 / 33   97%
PORTS        [10000]                   0 / 1     0.00%
MEM          128                       0 / 0     0.00%
DISK         0                         0 / 0     0.00%
CPUS         1                         0 / 0     0.00%

Processed offers is super confusing as a user. I want to know the last state of my cluster, not everything that has been processed. The detail table (last X) is the right number.

@tamarrow Addressed all requested changes except the add expected-table.txt comment. We do have dynamical parts of the lines, therefore I check the lines via regex. Is that ok for you or should we do some tricks to combine both variations?

@unterstein looks like some unit tests are failing: https://teamcity.mesosphere.io/viewLog.html?buildId=486173&buildTypeId=DcosIo_DcosCli_Ci&guest=1
once we fix those, lets merge away :D

@tamarrow thanks for pointing this out! I fixed the test fixtures, but currently the CI build is stuck at [Step 3/5] Step Wait for CCM Cluster (Command Line) failed, see https://teamcity.mesosphere.io/viewLog.html?buildId=489909&buildTypeId=DcosIo_DcosCli_Ci&tab=buildLog&state=81#_state=81
What can I do to fix this?


“Document this” code action does not work properly

Description:
“Document this” code action does not work properly (it does not replace existing documentation when rerunning the code action after changing the function signature)

By design, the idea was not to remove the existing signature when adding the docs for the new signature, this is because most of the time users tend to copy content from an old signature. Hence we'll not fix this behaviour.


x/crypto: acme autocert seems not to work with github.com/letsencrypt/pebble

I'm using golang.org/x/crypto/acme/autocert against https://github.com/letsencrypt/pebble. I keep getting this error message:

urn:ietf:params:acme:error:unauthorized: Order includes different number of DNSnames identifiers than CSR specifies

Googling that error message led me to https://github.com/letsencrypt/pebble/issues/304, which I think says that Pebble is a little more compliant with the spec than Let's Encrypt and Boulder are, and a CSR must include the domain in the SAN:

Thanks for reporting! And @felixfontein thanks for digging out the link to the previous Pebble issue. The Pebble behavior is indeed intentional. In the early days of Let's Encrypt we chose to accept CSRs that only specify names in the CN without specifying them in the SAN. That was probably a mistake, but a minor one, and correcting it now would introduce compatibility problems with little benefit.
Our general goal with Pebble is to be a bit stricter about things, not to match all behavior of other implementations like Boulder and Buypass. So we're planning to keep the current behavior. If you'd like to maximize compatibility between the three implementations, I think putting all names in the SAN should work.

Indeed, simply including domain in the SAN fixes the issue in my case: https://github.com/golang/crypto/commit/9860d605a5042280652d0aeeddc1f24782619181.

Thank you, we'd welcome a PR for this!


Resolve #73

This PR changes ConstantSet.compare back to String.compare from String.numeric_compare, which bumps the speed of encoding back up significantly and resolves #73. To make this change, we have to change how we determine the relevant SMT terms for each input expression: instead of searching through the declared constants, we store the full set of variables for each input. Right now, this is done at partitioning time, which unfortunately means that the type information of the attribute is not used to reconstitute the input hyp routes back together.
As a further modification, we should change this to properly use the transformations to map the values back.

Later commits have now resolved the issue with mapping back hypotheses, so this PR is all done. Has definitely exposed some other things that should be fixed later, but for now we have some improvements.


Provide instructions on how to make native JS launcher

There are currently no directions available for making the GraalVM JavaScript launcher as a native binary like the one provided in Community Edition builds of GraalVM. This information should be provided.

Hi,
can you please clarify what exactly you expect us to publish?
There already is extensive documentation for native-image available. The possibility to include Graal.js in your native image builds by just adding --language:js is mentioned even on the start page of native-image's documentation at https://www.graalvm.org/22.0/reference-manual/native-image/ As Graal.js is just one of millions of libraries that you might want to include in your application, I have to refer you to the native-image documentation on that, that is not something Graal.js would try to tackle and document. Again, from our point of view, it is enough to add  --language:js in order to bring Graal.js to your native-image build stream.
If you are interested in how we build our CE or EE releases, I believe there is near to zero documentation and I don't think we really plan on extending that short term. You will find most of that expressed in our mx scripts and related materials.
Best,
Christian

Hi,
can you please clarify what exactly you expect us to publish?
There already is extensive documentation for native-image available. The possibility to include Graal.js in your native image builds by just adding --language:js is mentioned even on the start page of native-image's documentation at https://www.graalvm.org/22.0/reference-manual/native-image/ As Graal.js is just one of millions of libraries that you might want to include in your application, I have to refer you to the native-image documentation on that, that is not something Graal.js would try to tackle and document. Again, from our point of view, it is enough to add --language:js in order to bring Graal.js to your native-image build stream.
If you are interested in how we build our CE or EE releases, I believe there is near to zero documentation and I don't think we really plan on extending that short term. You will find most of that expressed in our mx scripts and related materials.
Best, Christian

Yes, I am talking about the binary js that is available in the GraalVM CE builds. Given that it is the corresponding official build of Graal.js, one would think it customary that the build routine for making it would be included in the source code.

Instructions on how to build GraalVM - which is the preferred and most straightforward way to build Graal.js including the native launcher - can be found at https://github.com/oracle/graal/blob/master/vm/README.md
If you have all the repos ready (mx sforceimports in [Graal-Repo]/vm should pull them) you call mx --env ce build).
Based on that command, you might be able to come up with a slimmer version of the build command. E.g., for Graal.js alone, you might not need sulong for instance. For that, you can prepare a modified env file in [Graal-Repo]/vm/mx.vm/.
-- Christian


Stirring RPM measurement is biasing too high

Could be related to changes in #410, as I measured this on a develop Pioreactor.
RPM was saying ~500RPM, but when I filmed, I was getting ~360RPM.

nvm my counting method in the film was wrong. Using the film + a new method, I got 500RPM


[$1000]  Opening legal name from link and login does not display saved legal name

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app
If legal name is not set then set legal name using any value and copy URL, URL should be: https://staging.new.expensify.com/settings/profile/personal-details/legal-name
Logout
Paste the URL copied in step 2 and then login
Observe that previously saved legal name is not displayed

Expected Result:
App should display previously saved legal name when we visit legal name page
Actual Result:
App does not display previously saved legal name when we visit legal name page by link and login
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.3.39-5
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/da294b1e-2d7a-4f21-890b-6b55cb5ec007
https://github.com/Expensify/App/assets/43996225/81599a83-c095-4b25-9543-b45cfdc8d3be
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689008918453839
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01baaf1e728dd0c132
Upwork Job ID:<PHONE_NUMBER>246221312
Last Price Increase: 2023-07-13

Was able to repro this. So the difference is:

When you're logged in and navigate to https://staging.new.expensify.com/settings/profile/personal-details/legal-name, the page displays whatever Legal Name you have set
When you're not logged in and navigate to https://staging.new.expensify.com/settings/profile/personal-details/legal-name, the page displays Legal first name and Legal last name

@stephanieelliott This one is new and proposals are already there. I might not be able to look into this sooner, so please assign a new C+ here to take this forward. Thanks!

@allroundexperts Wrong person, you meant @c3024

Hi @dangrous, no I have just got one offer from service account, all good for this bug.

hi @allroundexperts! Let us know when you have a chance to review the PR - thanks!

Discussion continues on the PR

Shush melvin, we just merged the PR!

Looks good to me! about to chime in in Slack too - I think it would be worth having a checklist item saying something like "I verified that a direct deep link to the part of the App affected by my code change works as expected"

Regression test case issue here: https://github.com/Expensify/Expensify/issues/305639

Summarizing payment on this issue:

Issue reporter: @dhanashree-sawant $250 reporting bonus (paid via Upwork)
Contributor: @tienifr $1000 (paid via Upwork)
Contributor+: @allroundexperts $1000 (please request in newdot)

Upwork job is here, no speed bonus on this one

Reviewed the payment details for @allroundexperts. This is approved for payment in NewDot.


Add more diverse issue templates

Pull Request Etiquette

[x] I have checked the PRs for upcoming features/bug fixes.
[x] I have read the contributing guidelines.

Changes

[ ] Internal code
[ ] Library interface (affecting end-user code)
[ ] Documentation
[x] Other: New issue templates

Closes Issue: NaN
Description

I plan to cherry-pick this commit onto v4 afterwards to keep the templates in-sync across branches.


"Entity" classes are not created anymore - part 2 (previous one was #142)

Okay,
It's happening again.
I tried again to move between 18 and 16 but it didn't help.
I think that the issue is happening when I make changes in my Entity interfaces (not the generated files) and something is not configured properly.
The main issue is that I have no idea how can I check the problem and find the error.
Thanks a lot for any help and advice...

You need to check the cause of the build failure in Intellij/Android Studio its in the build output window. Otherwise run gradle build --stacktrace from the command line to get the output.

@danysz What version of gradle are you using?  When I built a snapshot of requery, I noticed I needed to use Gradle 2.12, which is newer than what ships with Android Studio.

I am using 2.10 and it's working


Update URL for Metacontroller

The Metacontroller project has moved from Google control to community support. This PR is to update the URL as the existing one no longer works. Ref: https://github.com/metacontroller/metacontroller#a-new-home

CLA signed

@2ZZ Welcome and thanks for your first PR to k8s! The change looks good to me.
/lgtm

/approve


Complete localization

First thing you'll notice is that everything is rearranged. I did that because your //item and //tile arranging has obviously died about 300 commits ago. I'm like 90% sure I didn't break the website, but check it, just in case.
Beside that:
-Fixed capitalization
-Made the highlighting more consistent
-Added puns. Lot's of puns.
-Added a tiny bit of personality to fairies :3

Also, if you don't like the way I rearranged things, I still have a copy with the fixes, but without rearranging. Just let me know and I will make a PR with that.


OS1-128 mapping error

Dear TixiaoShan, thank you for your brilliant work.
I tried SLAM with Velodyne lidar using your source code and succeeded.
Now I'm trying to use Ouster lidar but there was a mapping error.
I used the same sensor as you. (OS1-128, LORD IMU sensor)
What I changed in 'params.yaml' file is topic name, lidar model, number of channel, and horizontal resolution.

When I did roslaunch with ouster launch file, I defined timestamp mode as you mentioned.

I don't know the cause, but I can't map it. I've been trying to solve this problem for weeks. If you know anything about this, please give me some advice.

I also share my bag file here.
https://drive.google.com/drive/folders/1F_kMXPAdxfhmymauiMEeppUkxK9Gc26d?usp=sharing
Thank you!

LIO-SAM only works with a 9-axis IMU.

LIO-SAM only works with a 9-axis IMU.

LIO-SAM only works with a 9-axis IMU.

Yes. I used 9-axis IMU, but I failed mapping with OS1-128

LIO-SAM only works with a 9-axis IMU.

Yes. I used 9-axis IMU, but I failed mapping with OS1-128

Hi,
We are having what it looks like the same problem. We are doing the same as @JJuhyeon-Kim, with the same result.
I'm using the same Ouster OS1-128 with a Vectornav VN-100 IMU. We are using the official Ouster driver.
We have successfully used LIO-SAM with Velodyne and RSLidar with the same IMU previously, but we are not able to make it work with the Ouster.
Was the problem solved? How?
Thank you for your help.

Same problem, but with an Ouster OS0-64.

Same problem, but with an Ouster OS0-64.

FYI, in our case it resulted a problem with the Ouster driver not providing proper ROS timestamp if not synchronized by PTP. We solved it applying the proposed patch to the driver, but apparently this functionality has been already added recently to the latest release (we have not tested it yet).

For someone who run into this problem and found this issue, here are the solutions as of today:

Launch driver.launch in the ouster-ros package with timestamp_mode:=TIME_FROM_ROS_TIME instead of TIME_FROM_PTP_1588.
If you would like to use PTP and the timestamp of the data is about 37 sec behind the system clock, set ptp_utc_tai_offset to 0 for driver.launch in the ouster-ros package.


[Insight] Web applications should contain a favicon

in ./

No favicon found in the web root directory

Posted from SensioLabsInsight

Closed as invalid. Changed project type to "Other" in Sensio Insight as the "Web Project" type assumes that document root is the same of the project root.


Docker compatibility: Created timestamp returned by image list is in wrong format

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Podman's /images/json endpoint returns created timestamp as a string. Docker returns created timestamp in unix time. Different format causes popular tools such as testcontainers to fail.
Steps to reproduce the issue:

podman system service --log-level=debug --time=0 unix:///tmp/podman.sock

curl --unix-socket /tmp/podman.sock "http://localhost/images/json" -v

Describe the results you received:
"Created":"2020-06-23T11:06:02.096204727Z"
Describe the results you expected:
"Created":<PHONE_NUMBER>000
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version:      2.0.0
API Version:  1
Go Version:   go1.13.8
Built:        Thu Jan  1 02:00:00 1970
OS/Arch:      linux/amd64

@baude PTAL

https://docs.docker.com/engine/api/v1.40/#operation/ImageInspect suggests that our current format is correct.  I will keep digging to see if the documentation is in error.

Also just checked on ubuntu docker.
Docker version 19.03.8, build afacb8b7f0
ubuntu@ubuntu:~$ sudo curl --unix-socket /var/run/docker.sock http://localhost/images/alpine/json | jq .Created
"2020-05-29T21:19:46.363518345Z"

For inspect endpoint that is correct behavior, but for list of images created timestamp should be formatted as unix time (integer).
(This doesn't make any sense from API user perspective)

@skorhone my apologies. you are correct as i misread the report.  this is why i shouldnt work on the weekends.  confirmed as bug.

The PR was merged, should this issue be closed?

I think we can close it.

It looks like the issue isn't fixed:
% sudo podman image pull ubuntu:18.04

Trying to pull docker.io/library/ubuntu:18.04...
Getting image source signatures
Copying blob d13af8ca898f done
Copying blob 70799171ddba done
Copying blob b6c12202c5ef done
Copying blob 7595c8c21622 done
Copying config 2eb2d388e1 done
Writing manifest to image destination
Storing signatures
2eb2d388e1a255c98029f40d6d7f8029fb13f1030abc8f11ccacbca686a8dc12

% sudo podman images

REPOSITORY                TAG     IMAGE ID      CREATED      SIZE
docker.io/library/ubuntu  18.04   2eb2d388e1a2  10 days ago  66.6 MB

Note the Created timestamp format:
% sudo curl --unix-socket /run/podman/podman.sock http://d/v1.35/images/docker.io/library/ubuntu:18.04/json

{"Id":"sha256:2eb2d388e1a255c98029f40d6d7f8029fb13f1030abc8f11ccacbca686a8dc12","RepoTags":["docker.io/library/ubuntu:18.04"],"RepoDigests":["docker.io/library/ubuntu@sha256:767eea1efb29ab7e215e1d97c8d758df5d587ca86e769a2dfb254c6b022895c3","docker.io/library/ubuntu@sha256:a61728f6128fb4a7a20efaa7597607ed6e69973ee9b9123e3b4fd28b7bba100b"],"Parent":"","Comment":"","Created":"2020-07-24T14:38:22.027273323Z","Container":"eb731db74ec67b789f444e92270caaa9978f8156b6f168c9b24a33c8fb86c9bc","ContainerConfig":{"Hostname":"eb731db74ec6","Domainname":"","User":"","AttachStdin":false,"AttachStdout":false,"AttachStderr":false,"Tty":false,"OpenStdin":false,"StdinOnce":false,"Env":["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"],"Cmd":["/bin/sh","-c","#(nop) ","CMD [\"/bin/bash\"]"],"ArgsEscaped":true,"Image":"sha256:d70b4aa31e228d7eec1d350f2306d75a50b591c117441e8983f49d0b528d3896","Volumes":null,"WorkingDir":"","Entrypoint":null,"OnBuild":null,"Labels":{}},"DockerVersion":"18.09.7","Author":"","Config":{"Hostname":"","Domainname":"","User":"","AttachStdin":false,"AttachStdout":false,"AttachStderr":false,"Tty":false,"OpenStdin":false,"StdinOnce":false,"Env":["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"],"Cmd":["/bin/bash"],"Image":"","Volumes":null,"WorkingDir":"","Entrypoint":null,"OnBuild":null,"Labels":null},"Architecture":"","Os":"","Size":66626009,"VirtualSize":66626009,"GraphDriver":{"Data":null,"Name":""},"RootFS":{"Type":""},"Metadata":{"LastTagTime":"0001-01-01T00:00:00Z"}}

% sudo curl --unix-socket /run/podman/podman.sock http://d/v1.35/images/json

[{"Id":"2eb2d388e1a255c98029f40d6d7f8029fb13f1030abc8f11ccacbca686a8dc12","RepoTags":["docker.io/library/ubuntu:18.04"],"Created":"2020-07-24T14:38:22.027273323Z","Size":66626009,"Names":["docker.io/library/ubuntu:18.04"],"Digest":"sha256:a61728f6128fb4a7a20efaa7597607ed6e69973ee9b9123e3b4fd28b7bba100b","Digests":["sha256:a61728f6128fb4a7a20efaa7597607ed6e69973ee9b9123e3b4fd28b7bba100b","sha256:767eea1efb29ab7e215e1d97c8d758df5d587ca86e769a2dfb254c6b022895c3"],"History":["2eb2d388e1a255c98029f40d6d7f8029fb13f1030abc8f11ccacbca686a8dc12","\u003cmissing\u003e","\u003cmissing\u003e","\u003cmissing\u003e","\u003cmissing\u003e"]}]

Podman was installed from http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04/ on Ubuntu 20.04
% sudo podman --version

podman version 2.0.4

@max-arnold
https://github.com/containers/podman/blob/v2.0.4/pkg/domain/infra/abi/images_list.go#L55
https://github.com/containers/podman/blob/master/pkg/domain/infra/abi/images_list.go#L55
it didn't get into 2.0.4 but is in master, lets hope for 2.0.5

Thanks for the clarification! I'll try to build Podman from source, since packages are often lagging behind the releases...

@zhangguanzhang could you cherry pick this into the v2.0 release, then we know it will get into 2.0.5.
@mheon WIll be releasing 2.1 fairly soon, but getting this into the stable branch will have it show up RHEL8 and Centos 8.


Separate out generic application wiring from MaterialApp

Create another class, like App or BasicApp, that does things like wire up locale and media query information, but does not assume any particular UI layout the way MaterialApp does.
MaterialApp could then either inherit from this class, or hold one in a member variable, depending on which seems cleaner.

Related to #1129

I wonder if it should wire up a Navigator...

I don't have a strong opinion, but maybe leave it out for now? We can push navigator support down more easily than trying to pull it up later (since pulling it up would be an API removal).

Makes sense.

cc @jimbeveridge - are you saying this would be really good asap?

I've manually extracted the bits in SysUI, but it would certainly be cleaner if it were properly factored and reusable. It doesn't need to be done before the Hackathon, if that helps.

Which parts did you use in your extracted version? Or maybe more importantly, which parts did you leave out?

I needed the ability to detect rotation and have my build function called
after rotation. I included the locale code, but we don't use it at the
moment.
Jim Beveridge
On Wed, Feb 17, 2016 at 9:27 AM, Ian Hickson<EMAIL_ADDRESS>wrote:

Which parts did you use in your extracted version? Or maybe more
importantly, which parts did you leave out?
—
Reply to this email directly or view it on GitHub
https://github.com/flutter/flutter/issues/1346#issuecomment-185313466.

So no navigator or overlay?

We use both Navigator and the overlay, but I didn't touch those classes in our code when I pulled out the bits from MaterialApp.

so it should probably include everything except the theme and the material grid. k.


Add ability to use logs, ssh, and scp commands with BOSH directors

3 new flags are added to the logs, ssh, and scp commands:

--director targets the director's agent HTTP endpoint
--agent-endpoint corresponds to the agent's HTTP endpoint, reference the cloud_provider.mbus property of the director manifest
--agent-certificate corresponds to the certificate provided to the agent's HTTP endpoint, reference the cloud_prodvider.cert property of the director manifest

The functionality of all of these commands is the same as without the --director flag, with the exception of using a private key/username (which doesn't make much sense in this context).
This flag is --director for simplicity, and we imagine that it will mostly be used with BOSH directors, but this feature works with any VM created with the bosh create-env command.
This feature depends on bosh-agent code that is present on stemcell versions:

Jammy: 1.93
Bionic: 1.181

The error when the agent does not support the command looks like:
$ bosh logs --director
Agent responded with error: unknown message bundle_logs

Exit code 1

@ragaskar, you did make me think of a situation where an error message could be improved, which is in 6017e1b4320e0011ba6c99d4391c219af738729d.

As an aside, I did find that even with older versions of the agent, you can use bosh ssh --director and bosh scp --director, since those actions have existed in the agent for a long time.  Only the bosh logs --director requires the updated stemcell to function properly.

@selzoc can you fix conflicts and we can merge after

@lnguyen fixed! :shipit:


Use AccessTokenPlugin only after login

Hi,
I am trying to use the AccessTokenPlugin functionality and i have some issue with it.  I need to find a way to initiate the AccessTokenPlugin only after my users are logged in and they have a token.
Currently in my Moya implementation I am creating the provider in the following way:
let token = ""
let authPlugin = AccessTokenPlugin(tokenClosure: token)
let myProvider = MoyaProvider<API>(plugins: [authPlugin])

enum API {
    case loginUser(username: String, password: String)
    case createUser(user: User)
}

extension API : TargetType, AccessTokenAuthorizable {
...

I need the JWT bearer to all the requests except the login and the creation of new users.
The problem is that i need to find a way to set the token only after the users are logged in. I was thinking about creating a new provider and override the old one but i don't understand if this is the recommended way to go with.
Can you please advice?
Thanks.

Hey @ranhsd. Right now to add a token you need to specify when/how you want to add it (by implementing AccessTokenAuthorizable) and what you want to add (by using tokenClosure). The first one should give you the ability to manipulate when/how you want to add it. You can have a default extension that you would always want to add the token, but in your login/register endpoint you would not send it with the request, e.g.:
extension API: AccessTokenAuthorizable {
    var authorizationType: AuthorizationType {
        switch self {
            case .loginUser, .createUser: .none
            default: return .bearer
        }
    }
}

Let me know if it's what you are looking for.

Hi @sunshinejr
Thanks for your quick response.
It’s really what I meant. I need to know when I can set the plugin to the provider. Because the first time that I create the provider and the user is not logged in I don’t really have the token I need to set the plugin on the provider only when I really have it (after user logged in and access token returns from the server) but I already initiate the provider before with the plugin. I need to find a way to recreate the provider again but this time to send the access token to the plugin
If you need more info please let me know
Thanks,
Ran

Oh, I think I understand the issue now. We had this problem before, so we changed the plugin lately that you don't have to specify token when registering the provider. Now we have a tokenClosure, instead of a token, so you can specify a way of getting your token instead of a token itself. We also added a convenience autoclosure keyword, so even a string is accepted by this plugin (thus why the code you posted works as well).
So, let's say that you save your token in a keychain. You can initialize a provider even though you don't have your token yet:
let tokenClosure: () -> String = {
    return Keychain.getToken() // here you can specify how to retrieve a token
}
let authPlugin = AccessTokenPlugin(tokenClosure: tokenClosure)
let myProvider = MoyaProvider<API>(plugins: [authPlugin])

Does this resolve your problem now, @ranhsd?

Hi @sunshinejr
it looks better. The question is if the tokenClosure will be executed in each api call ?
Thanks!
Ran.

Yes, @ranhsd. Each time there is a request the plugin evaluates the tokenClosure just before the request, here. No caching involved.

@sunshinejr Thank you very much!!

Glad it helped! 🎉

@sunshinejr Hi, referencing your comment on Oct 25 I am passing a closure to the AccessTokenPlugin
            let tokenClosure: () -> String = {                 return token             }             let authPlugin = AccessTokenPlugin(tokenClosure: tokenClosure)             return MoyaProvider<T>(manager: manager, plugins: [authPlugin])
However the complier gives me the following build time error:

Function produces expected type 'String'; did you mean to call it with ()

Can you give any information about why I am getting this error?
XCode: 9.2
Swift: 4.0
Thanks

@sunshinejr
Hi, it is having an error when I follow your sample code.
Xcode Error: "Function produces expected type 'String'; did you mean to call it with '()'?"
Could you advise this issue, please?
let tokenClosure: () -> String = {
    return "Any string"
}
let authPlugin = AccessTokenPlugin(tokenClosure: tokenClosure)

@sunshinejr
I finally solved this issue by using code below, hope it could help who are facing the same
var tokenClosure: String {
return "Any string"
}


Protect Poi data against XSS

Does favorites_panel.dot file can be included too to this commit ?

🍾

merci @patfrat


add routing promise

routing should refer to the same promise returned by route(), until it resolves, and then it should be null.

@aaronshaf Would this satisfy the need in #11?

Looks good. Thank you!

fixes #11


fix(debugger): Update the debugger to handle the new Brillig debug metadata format

Description
Problem*
Resolves #5703
Summary*
After https://github.com/noir-lang/noir/pull/5696 debug metadata from Brillig functions was de-duplicated to avoid a blow-up in artifact size. The debugger uses this debug metadata format to accurately display information in the REPL and DAP interface. This PR contains the updates needed for the debugger to handle the new debug metadata format.
The debugger on inline_never_basic (the example used in the linked issue) gives the following again:

The output matches what was on master before PR #5696.
Additional Context
Documentation*
Check one:

[X] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

It won't let me request your review directly due to you not being in the org so cc'ing @anaPerezGhiglia

I'm leaving just some minor suggestions on this.
@ggiraldez or @mverzilli can you review the juicy part of this PR? If not I can take a deeper look into it next week

As to unblock #5703 we're going to merge this for now and any other work can come in a follow-up.

We checked locally and this indeed fixes our tests that were broken by the introduction of the bug.
Thanks for the quick turnaround!


Why did you call BasicLSTMCell a cell and not a layer?

BasicLSTMCell is actually a layer (as for a layer in MLPs) of LSTM units. Each of these LSTM units contains a cell. Each cell of an LSTM unit contains a scalar value for the CEC and a scalar representing the previous state.
People are usually first introduced to MLPs or feed-forward (and fully connected) neural networks, before being introduced to RNNs and, in particular, LSTMs.
Why would you call BasicLSTMCell a cell, if it can be thought more intuitively (at least for me) as a layer of LSTM units (as I describe them above) containing just one scalar-based cell? Wouldn't it be less ambiguous to call a BasicLSTMCell BasicLSTMLayer???
Moreover, the first parameter to BasicLSTMCell's __init__ method is num_units, i.e. the number of LSTM units, i.e. the number of LSTM cells and gates (if we have 3 gates for every LSTM unit, then the total number of gates in one layer of LSTMs is 3 * num_units).
It almost seems that you created TF to make it as confusing as possible to make it seem hard. It also almost seems that the person who wrote the name of the class BasicLSTMCell is a different person of the person who wrote its __init__ method. What's going on??? A little bit of consistency, for once, no???
A similar argument can be said for MultiRNNCell, which, a lot more intuitively, can be thought as a sequence of layers.
Request
Change classes such as BasicLSTMCell and MultiRNNCell to have more descriptive names of what they actually are in future versions of TF. Then change the corresponding documentation to be more compliant with these changes.

We work hard on building clean and consistent interfaces, but the truth is that the field moves quickly, and the description and terms used when an idea first breaks out aren't always the same as the best way to teach things turns out a few years later. And we also have a responsibility to our users to maintain some backwards compatibility with the older (and probably uglier) interfaces. I think in practice we can add new, cleaner interfaces, but it's a slower process to deprecate and remove the older, uglier ones.
I think @ebrevdo wrote the code in question (both the class and its init method). He might be able to comment on future, cleaner interfaces.

Nomenclature varies between different researchers.  It's unfortunate that the naming doesn't match standard notation taught by NN courses, but this interface is locked for backwards compatibility until at least tf 2.0 due to our API guarantees.  You may have an easier time with the naming in the Keras API.  Will add this request to the internal list of possible breaking changes for future versions.  Closing.

@ebrevdo Yes, nomenclature varies, but I am more concerned about consistency within the same class, module and possibly library.
The "cell" BasicLSTMCell contains a method called __init__ whose first parameter is num_units, which is vaguely documented as

The number of units in the LSTM cell.

Number of units??? Which units??? A cell has units???
At least, meanwhile, you should change the documentation to make it more understandable!!

Would you like to submit a PR to help improve the documentation?  I'm happy
to review.
On Sun, Nov 19, 2017 at 6:03 AM, Nelson Brochado<EMAIL_ADDRESS>wrote:

@ebrevdo https://github.com/ebrevdo Yes, nomenclature varies, but I am
more concerned about consistency within the same class, module and possibly
library.
The "cell" BasicLSTMCell contains a method called init whose first
parameter is num_units, which is vaguely documented
https://www.tensorflow.org/api_docs/python/tf/contrib/rnn/BasicLSTMCell
as
The number of units in the LSTM cell.
Number of units??? Which units??? A cell has units???
At least, meanwhile, you should change the documentation to make it more
understandable!!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/14693#issuecomment-345519132,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtimxO70QZgMLDIemq8Iluxxjsz1heVks5s4DUogaJpZM4QjErd
.


Update dependencies

This update is needed for rtc_engine to work correctly in all the scenarios.

Create new PR with proper name


Device unable to go to light sleep with PCNT unit enabled without glitch filter (IDFGH-14231)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
In ESP-IDF 5.3.1 and before, the APB frequency lock was only used if the glitch filter was enabled for a PCNT unit. This allowed the device to enter light sleep even when a PCNT unit was enabled (but without a glitch filter).
In ESP-IDF 5.3.2 the commit https://github.com/espressif/esp-idf/commit/33f82075e96da7c4cfa941391604ab6cd11316d2 introduced new behavior, and the lock is always installed and used, even if the glitch filter is not enabled.
This means that since 5.3.2 the device cannot enter light sleep when a PCNT unit is enabled, even if it uses no glitch filter.
The commit comment says "fix" but I found no record of what problem this is fixing.
The documentation in 5.3.2 still says the lock is installed lazily only when a glitch filter is present:
 *       So this function will lazy-install a PM lock internally when the power management is enabled. With this lock, the APB frequency won't be changed.

https://github.com/espressif/esp-idf/blob/v5.3.2/components/esp_driver_pcnt/include/driver/pulse_cnt.h#L128

Thank you for your feedback.  We've left some documentation unchanged. In fact the APB clock is the function clock for the PCNT peripheral, not only for the glitch filter. The previous version was actually not correct.


TPI: Python REPL Run Recent Command Current Session

Refs: #22647

[x] macOS @hbons
[x] linux @andreamah

Complexity: 2
Create Issue
Create Issue

Thank you in advance for testing this feature!
Today we will test Terminal: Run Recent Command for Python REPL, specifically
More background information about what this does can be found here in official VS Code documentation:
(https://code.visualstudio.com/docs/terminal/shell-integration#_run-recent-command)
Setup:

Make sure you have Python installed in your computer.
Make sure you have not turned off terminal.integrated.shellIntegration.enabled (You shouldn't worry about this if you haven't touched this setting manually yourself)

Steps:

Open Python file. (aka. .py file)
Launch Python REPL via Shift+enter or other key binding to launch Python REPL inside VS Code.
Execute code in the REPL via Shift+enter
Press control+shift+p, command+shift+p and then type Terminal: Run Recent Command to see if your Python REPL command history exists for current session

works! no problems found.

works great for me! 👍


feat: add more q & a

Hello @AkashRajpurohit
a new portion of q & a from Laura.
Starting from the ~q#53~ q#52 there are q&a from the "interview edition", not sure what's your view on it, should we put them with the rest?
Regards ,Eugene

LGTM, thanks @etolbakov for adding these and @bew for initial review.


${page.path} returns undefined - should be changed to ${page.url} if it' the url that it should output

Request Type

[ ] Small Fix (wording, errors, typos, etc.)
[ ] Explanation Improvement (make a description clearer for the reader of the docs)
[X] Walkthrough Request (new tutorial for a particular feature or use case)
[ ] Other

Description
While going through the guide guide - Section Page Variable, the tutorial says

The current page path is: {$page.path}
but it returns undefined.

What would you like to see improved?
I think it should be {$page.url} instead
If improving on existing content, where is that content located?
guide
Are you interested in contributing this improvement to the docs?
Yes, but I'm sorry, I'm not a real dev and I don't know how to do PRs
Feel free to open a pull request with your suggested changes to the docs! If you're interested in contributing, but you need help, please let us know here or in Slack and we'll be happy to help you get started.
P.S. Some screenshots
${page.path}

${page.url}

Good catch - I think SvelteKti has updated {$page.path} to {$page.route.id}


Galactic Civilizations III requires DxgiOutput::FindClosestMatchingMode

Software information
Galactic Civilizations III, current Steam version
Crashes on start with "Fatal error: Failed to initialize display."
System information

GPU: Radeon RX 480
Driver: Mesa 17.3.2
Wine version: 2.21-staging
DXVK version: git fd1fd40

Apitrace file(s)
todo
Log files

d3d11.log: (empty)
dxgi.log: https://pastebin.com/Ks1gYbyS

Fixed by #153.


Question: Community maintenance of deprecated controls

I have a question regard to the maintenance of deprecated controls.
With WinUI3 some control elements of UWP are no longer being developed. #3957 What are the controls that are no longer being developed and is there a possibility that the community will take over these controls for further development?
The pivot control in particular cannot be replaced by other controls due to some of its properties. For example the change of view without navigation and touch based interaction to other Pivot items (swipe left or right).

@ryandemopoulos FYI


Release bv4

Hey guys,
after Foundation launched his v6 yesterday I wonder when does bv4 comes out? Any vague idea?
Keep up.
Thanks

🔜
(The alpha is already out.)

Alright. Regarding this list http://blog.getbootstrap.com/2015/08/19/bootstrap-4-alpha/ it's a very very late soon. I thought it would be a race between f6 and bs4 ;)
Till next year then.

http://blog.getbootstrap.com/2015/12/08/bootstrap-4-alpha-2/


labels: Add LabelDistributionSource

Add a public const for "containerd.io/distribution.source" in labels package and replace hardcoded usages.

/ok-to-test

@AkihiroSuda ptal (related to https://github.com/moby/moby/pull/44963#discussion_r1101794386)


Document SQL dialect guidance

Which issue does this PR close?

Closes https://github.com/apache/datafusion/issues/13704

Rationale for this change
Determining what  is the "correct behavior" comes frequently deciding how a function should behave and there is disagreement across implementations (e.g. postgres does something different than spark and/or duckdb)
This happened most recently here with @comphead and @jayzhan211 and @Kimahriman in https://github.com/apache/datafusion/pull/13683#issuecomment-2526344085
What changes are included in this PR?

Try and document what the current behavior is (please double check me here)

Are these changes tested?
By CI

Are there any user-facing changes?
New docs page.
In my mind this doesn't change any semantics or policy, it simply documents the current reality. However, I am not 100% everyone has the same understanding of the current reality 🤔

Update: I don't feel like we have reached consensus on this ticket yet, so I don't have any specific plans to merge it yet

I removed @comphead's approval so it was clear this PR is not ready to merge (from my perspective)


GetAsync() and Include

There seems to be an issue with the GetAsync() method. I'm writing a small library to maintain the database of my private mail server and tried to query a SQLite database. The "MailAccount" class contains a property to the "Domain" the mail account belongs to. Furthermore a property of type long annotated with the ForeignKey attribute points to the "Domain" property.
The following line works as expected:
MailAccount account = connection.Get(new MailAccount { Id = id }, statements =>statements.Include<Domain>(x => x.LeftOuterJoin()));
The asynchronous equivalent does not:
MailAccount account = await connection.GetAsync<MailAccount>(new MailAccount { Id = id }, statements => statements.Include<Domain>(x => x.LeftOuterJoin()));
Is there something I should additionally consider when using the asynchronous API functions?

What issue are you experiencing?

An InvalidOperationException is thrown when calling GetAsync().
Exception Text:
Invalid attempt to call FieldCount when reader is closed.
Stack Trace:
   at Microsoft.Data.Sqlite.SqliteDataReader.get_FieldCount()
   at Dapper.SqlMapper.GetColumnHash(IDataReader reader, Int32 startBound, Int32 length)
   at Dapper.SqlMapper.<MultiMapImpl>d__139`8.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)
   at Dapper.FastCrud.SqlStatements.RelationshipSqlStatements`1.<SelectByIdAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at CloudyCube.Api.Persistence.Repositories.MailAccountRepository.<GetByIdAsync>d__3.MoveNext() in D:\Visual Studio Projects\CloudyCube\CloudyCube\src\ManagerAPI\Persistence\Repositories\MailAccountRepository.cs:line 59

Oh. if it matters, I'm using .NET Core 1.0.1.

Dapper is suffering from a bug that causes the async methods to fail.

Ok, I'll try to work around it. Thank you very much for the explanation!

Hi.
I am having the same issue. But i get:
"<System.InvalidOperationException: No columns were selected".
The normal Get works, but not the async.

 Maybe even underline It.
Do you know that  GetId will block and you will block one of the very important threads for the Task Scheduler? You didn't even use long running flag so It's super likely to completly shutdown your application If your application.
For anyone looking at this DO NOT USE IT! It will cause alot of unwanted behvaiour.

Omg. What language you have young man.
It isn't nice to call people "super retarded".
If you are a better programmer then it is best to give an example of how to do it.
But as far as I know.
Calling
var actual = await foo.GetIdAsync(1, session);
Shouldn't block.
Yes it will use a thread in the thread pool. But that is it.
Have a look at who to make async methods:
https://msdn.microsoft.com/en-us/library/hh873177(v=vs.110).aspx

internal Task RenderAsync(
              ImageData data, CancellationToken cancellationToken)
{
    return Task.Run(() =>
    {
        var bmp = new Bitmap(data.Width, data.Height);
        for(int y=0; y

@GroundZero Any Comments?

I'm still facing this issue
An InvalidOperationException is thrown when calling GetAsync().
Exception Text:
Invalid attempt to call FieldCount when reader is closed.


Gateway incorrectly reports a managed domain

The gateway FVjKQYTXoUmdyhs9nKh3yqVRnsvG4bSyh6wYLHReWKeW reports that it manages gateway.tf, but deploying a subdomain on it gives this error:

@delandtj did fix this gateway


(ui polish) switching from bar charts to pie charts for an easier comparison

The bar charts from MpAndroidChart were a bit hard to read, so I decided to swap them out with pie charts instead that show the percent of the spending limit that has been used. (If the percent exceeds 100%, the circle is completely filled but the percent shows accurately.)

Aw man I think I forgot to rebase after the last pull request? I'll squash and merge though

LGTM! Thanks for the additional polish and code care!


Make new harness fake host more performant in large complications

This fixes some of the issues our RWC suite has with the new vfs-backed test harness.
The changes include:
First: empty path segments will now be collapsed by our path handling logic (as they were before). We had tests exhibiting a dependence on paths like ../..//site/SomeFile.ts resolving correctly.
Second: Do not attempt to regex away comments from .json files inside vfs.System. Instead, just use parseConfigFileTextToJson in the moduleNameResolver to allow for comments in parsed package.jsons (after all, we handle them in every other json document we parse, so why not there) - the regex used for finding comments and stripping them at the system layer had a catastrophic bad case in the RWC suite; our own parser should be more predictable (and more importantly, if it exhibits similar problems in the future, must be fixed).
Third: Replaces outputs in the fakes.CompilerHost with a canonicalized map and ordered list of names - linerarly searching for the insertion index in the output list took forever when there was > 2000 files in the output (as shown by our largest RWC tests) - this remedies that pathological case.
I think the VFS is still the root cause of some other RWC failures related to being unable to find a tsconfig, but I haven't gotten a chance to look into that yet, so that'll probably be separate.

I don't think we should modify outputs as it's a verbatim list.

Modifying it is precisely what we were doing before. (And was why it was slow) Now its generated on demand and isn't searched through for insertion positions.

Modifying it is precisely what we were doing before.

You are correct, sorry. That's what I get for trying review a PR over my phone.


list avds not working in high sdk

Fix issue: https://github.com/selendroid/selendroid/issues/1107
Incompatible with SDK Tools 25, command "list avds" does not exist

Could you upload corrected jar?

new jar file should be uploaded to official site.

Does anyone know when this will be fixed :( ?

@dmitrikudrenko actually was stuck with building jar file, follow the instruction in official site
When I run mvn package, it somehow cant fetch repos of:

[WARNING] The POM for android.support.test:runner:jar:0.5 is missing, no dependency information available
[WARNING] The POM for android.support.test:exposed-instrumentation-api:aar:0.5 is missing, no dependency information available
[WARNING] The POM for org.apache.cordova:cordova:jar:android:3.7.0 is missing, no dependency information available
[WARNING] The POM for org.apache.cordova-android:cordova:jar:android:4.0.0 is missing, no dependency information available
[WARNING] The POM for com.google.android:support-v4:jar:21.0.3 is missing, no dependency information available

Then failed to build:
selendroid-server .................................. FAILURE

This would break for older installations. I believe #1136, fixes it in a backwards compatible way. I'm waiting for the author to  rebase before we can merge it

This was fixed in #1136


Cemu 2.0 is experimental

The version of Cemu installed by this bucket is 2.0, which is currently an experimental pre-release and is not considered stable. Is this deliberate? It'd be nice for it to install the latest stable 1.x instead

They just haven't updated the site yet but on github there is no longer marked experimental on the 2.0 tag.
It's probable that a 2.0.x will be marked "stable" soon as well.
At this point it doesn't make sense to change it.
There is also 1.27 old experimental version in-between 1.26 and 2.0
Is there a compelling reason to keep using 1.26 over 2.0?

Is there a compelling reason to keep using 1.26 over 2.0?

I've only really been playing Breath of the Wild, but for me it crashed every time I reached a very early cutscene with 2.0, whereas 1.26 has been completely stable.

They just haven't updated the site yet but on github there is no longer marked experimental on the 2.0 tag.

Looking at their GitHub releases, I can see the original 2.0 release from August but as far as I can tell, that was released when the 2.0 announcement post was made, which states that it should be considered experimental. Every release since then has been explicitly marked experimental.

It's probable that a 2.0.x will be marked "stable" soon as well.

Do you have a source for this? The original announcement described it as a big change, so without further information I'd guess that it might also take a while.

I suppose we could make cemu.json point to the latest 1.x release, but this will break existing installations of the "stable" package

Ahh, this is very true though. Maybe there's not much that can be done right now then apart from wait for a stable 2.0 release soon.

@eboddington They orginally marked the 2.0 release as experimental on github, but changed it. github would be the best source of truth over the site, which the devs don't update as often.
if you want to use cemu 1.x, you can install cemu from this bucket: https://github.com/borger/scoop-emulators
I maintain that repo and the same manifests in this repo.
Have you tried the latest 2.0.x release to see if it crashes? the latest 2.0.x release is listed as cemu-dev in that bucket.
I recommend trying the latest 2.0.-17 release since it's just bug fixes and improvements to 2.0.
As for my source: I follow their development on github and discord and discussions with the dev team, also being a dev myself.

@Calinou I can bring over cemu-dev which has the latest 2.0 release (which I recommend over 2.0 since it's just bugfixes).
It's kind of a rock and a hard place with cemu.json right now. You will have ppl upset no matter what you do.

Feel free to open a PR to update cemu-dev :slightly_smiling_face:

@beyondmeat ok, fair enough. I haven't installed the latest release to be fair, so perhaps it's sorted in that. Agree that not much can be done to sort out cemu.json now, and personally I will probably stay on my manual installation until 2.x is officially declared stable and available here, and then switch back to that. It's working fine, no reason for me to switch to 2.x yet personally.

I think it's best to keep things as they are now.


Where is the vgg16 pretrained modelS with BN?

Hi，
Thanks for your sharing！ But I cannot find the VGG16 pretrained models with BN. I'm very appreciated it if you release it.

Hi, I really appreciate sharing the trained weights.
Could you share VGG16 with BN?

I emailed the head of their department!
There does not seem to be a VGG16 as expressed in their web page! I assume it was a typo.

He has answered it in #16 !


2018 Updates

3D perovskites are up to 22.7% - not sure about the rest https://www.nrel.gov/pv/assets/images/efficiency-chart.png

Thanks Aron, this has been addressed in 28ea006.


Flip the type of linv

I know it's not convenient to change, but I think it will be a pain in the long run to leave it in the current direction. I think I updated everything except for some large terms in
new_brunerie_adjusthcom.cctt
new_brunerie_adjusthcom_2sym.cctt
new_brunerie_debug.ctt
new_brunerie_debug2.ctt
new_brunerie_debug3.ctt
new_brunerie_debug4.cctt
new_brunerie_debug5.cctt

where I don't understand where they come from.

That looks great, it's a big help indeed! Sorry for the state of Core.hs...


[Enhancement] Dark Mode

As the title suggests, i would like a Dark Mode for the UI because it is very tiring to look at white.

I won't be adding in a dark mode. Unfortunately, the UI toolkit used doesn't allow you to easily modify the look to create a dark mode

I won't be adding in a dark mode. Unfortunately, the UI toolkit used doesn't allow you to easily modify the look to create a dark mode

Damn...


removed align_corners=True

Got this error in Pytorch 1.1.0:
TypeError: grid_sample() got an unexpected keyword argument 'align_corners'

Hello,
Hmm.. we merged pull request align_corners = True for PyTorch 1.3.0 or later. https://github.com/clovaai/deep-text-recognition-benchmark/pull/91
However, I think we don't need align_corners = True until PyTorch 1.4.0 since it has no compatibility with previous versions.
So, for now, I agree to remove align_corners = True


[BUG]: directory data/data-3rd-party/ missing

When trying to run some commands it requires a directory and files that I could not find any documentation of how to create/download them.
Here are some examples:
./canswim.sh modelsearch
(...)
handle = open(
^^^^^
FileNotFoundError: [Errno 2] No such file or directory: 'data/data-3rd-party/all_stocks.csv'
./canswim.sh gatherdata
(...)
data/data-3rd-party/broad_market.parquet. Error: [Errno 2] No such file or directory: 'data/data-3rd-party/broad_market.parquet'
(...)
OSError: Cannot save file into a non-existent directory: 'data/data-3rd-party'
After I created the directory and run 'gatherdata' option again, I got:
Could not load data from file: data/data-3rd-party/industry_funds.parquet. Error: [Errno 2] No such file or directory: 'data/data-3rd-party/industry_funds.parquet'

These are valid questions:
Due to the licensing requirements of the yahoo and fmp APIs used to acquire market data, you would have to fetch the data before running model search, train and forecast.
Grab an FMP API Key and plug it into your local .env. You can use this example env file as a template:
https://github.com/ivelin/canswim/blob/main/example.env
Then run
canswim.sh gatherdata
that will populate the data directory for consequent modelsearch, train and forecast task runs.
Alternatively if you prefer to use a different API provider, feel free to change the source code using the FMP API. I would welcome a pull request making the API provider a configurable option.