A general way of using [ExportMetadata("Order", ...)]

ATF currently provides the option to adjust the order in which classes are initialised, using [ExportMetadata("Order", ...)]. Though I try to use this as little as possible as it makes components less generic, I've come to see that sometimes it's unavoidable.
It would be very useful if there were some API that made this order a bit more generic, and if it were used in the first place in the components. I haven't quite figured out yet how this would look, maybe you guys have some idea on this. Maybe something like and enum ImportOrder and then putting this on the components/services on which order matters.
Also, maybe the default for this value shouldn't be INT_MAX. For example, it is extremely useful to have Composer being initialised as early as possible, but I currently have no way of ensuring it's initialised before my other components. That is, not without touching the ATF framework myself at least.
Hope this makes sense.

Thanks for the suggestion, one of us will look into this.
Alan

At point the [ExportMetadata("Order", ...)]  is not used for controlling initialization order. It is declared in Atf.Wpf section which is work in progress.
Generally MEF does a pretty good job of negating the need to explicit control the order.
In some cases IPartImportsSatisfiedNotification can be used for component that obtain dependencies via  [Import] instead of [ImportingConstructor]
Thanks
Alan

Hi Jelle,
That usage of ExportMetadataAttribute in ATF was inadvertent. One of our clients uses it, but we did not copy over the mechanism that looks at that attribute. The sorting mechanism would be very similar to this post:
http://stackoverflow.com/questions/1770297/how-does-mef-determine-the-order-of-its-imports
I don’t think we should use this ExportMetadataAttribute in ATF in this way. There are a variety of ways to control the initialization order that are more obvious and lower-maintenance than having a numerical explicit order on the component.
•	You can implement MEF’s IPartImportsSatisfiedNotification, which has the OnImportsSatisfied() method. This method will get called by MEF when all of the imports have been satisfied.
•	Your component’s IInitializable.Initialize() method will be called after composition, and so all of the objects in the TypeCatalog will have been created, and then you can do further initialization.
•	You can have lazy imports, to get around a circular dependency. For example: [ImportMany] private IEnumerable<Lazy> m_documentClients = null;
•	You can override AtfApp’s OnCompositionBeginning() to acquire certain types of objects from your CompositionContainer, to make sure that certain objects are initialized first.
•	You can override AtfApp’s OnCompositionComplete() to do last-minute initialization of certain objects.
Can you please try some of the above ways? If these are not sufficient, then we can try to support ExportMetadataAttribute with an “Order” property and an integer value. Otherwise, I’d like to remove that one usage.
--Ron

Hi Ron and Alan,
Thanks for your answers. I think one of those solutions might be the right one, but I need to delve into it a bit more.
Let me outline the problem, to give a bit more context. I am using the CommandServiceExtension, which is extremely useful for binding to commands directly from XAML. The only problem is that this XAML is part of an import. In the CommandServiceExtension class, it is required that the Composer and the CommandService be imported and ready, and to actually use it, your command has to be imported already too. The nasty thing about a MarkupExtension is that ProvideValue() is only ever called once and then never more, so if any of the aforementioned required imports haven't happened yet, the command binding will be invalid forever.
Hence my need for the import order.
I think forcing those to be loaded OnCompositionBeginning() might work, to it'd be a hacky way. IPartImportsSatisfiedNotification isn't going to help here, methinks. Perhaps I can make all my XAML Lazy loads indeed, but I'd have to check if my application allows that.
All the best!
Jelle


Add extra button to modify inputs like The Antagonist board?

Ok so this is not an issue, it's more like a feature request... I'm sure you guys have heard of The Antagonist by now. It's a mod board that adds a button to modify inputs and adds hitbox-like features to lever controllers.
For example, if you hold back and press the extra button, the input changes to forward.
It sounds like a feature that should be very useful on the GP2040, so I'm wondering if it would be feasible to add it?

Hey @gamecenterjun ,
I know Buttero very well!
At this time we are not looking to implement things into the build that are produced by independent makers.
The Antagonist offers a number of features that we currently do not such as the mobile app for configuration.
I would recommend grabbing one of his boards, they are great!

Hey @gamecenterjun ,
I know Buttero very well!
At this time we are not looking to implement things into the build that are produced by independent makers.
The Antagonist offers a number of features that we currently do not such as the mobile app for configuration.
I would recommend grabbing one of his boards, they are great!


YCSB db size too small.

Default ycsb config for workloadb (95% read, 5% update) on n1-standard-8 doesn't issue disk reads with newer cassandra version (2.1.10), the entire db fit in memory.

@yuyantingzero I fix this problem by change workload file, you can change there number of columns in each record, size of column and number of rows (db size).

The current configuration populates the database with ~1GB of records. This is certainly too small for stressing Cassandra - I usually increase this to at least 2x the total memory of the cluster (via --ycsb_recordcount).
I'm OK increasing the default, but for in-memory cases (Aerospike if it's not configured to use disk, Redis) we need to keep the database size relatively small. How about for MongoDB, Aerospike (disk only), HBase, and Cassandra increasing the default recordcount to 2x the total memory of the data serving nodes?


Fix welcome fab menu doesn't show up

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/26076
PROPOSAL: https://github.com/Expensify/App/issues/26076#issuecomment-1739495776
Tests

Sign out from staging and localhost expensify
Go to staging.new.expensify.com
Enter new email address
Copy link address of Click here to sign into your Expensify account, like magic!
Modify the link: change the https://new.expensify.com into http://localhost:8082 and open it in browser
Click  just sign in here link
Notice the Welcome FAB menu appears.

Other test:

Sign out from expensify localhost
Register new email address in expensify localhost
Copy link address of Click here to sign into your Expensify account, like magic!
Modify the link: change the https://new.expensify.com into http://localhost:8082 and open it in new tab
There will be a note to come back to the first tab when registering new email address. Come back to that tab
Notice the welcome fab menu appears

For native IOS, Android and Macos Desktop

Sign out and then register new email address and enter the magic code
Notice the welcome FAB menu appears.

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Sign out from staging and localhost expensify
Go to staging.new.expensify.com
Enter new email address
Copy link address of Click here to sign into your Expensify account, like magic!
Modify the link: change the https://new.expensify.com into http://localhost:8082 and open it in browser
Click  just sign in here link
Notice the Welcome FAB menu appears.

Other test:

Sign out from expensify localhost
Register new email address in expensify localhost
Copy link address of Click here to sign into your Expensify account, like magic!
Modify the link: change the https://new.expensify.com into http://localhost:8082 and open it in new tab
There will be a note to come back to the first tab when registering new email address. Come back to that tab
Notice the welcome fab menu appears

For native IOS, Android and Macos Desktop

Sign out and then register new email address and enter the magic code
Notice the welcome FAB menu appears.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/114975543/d61febef-b9ba-42a6-9b74-17ce22a8dfdf

Android: mWeb Chrome
https://github.com/Expensify/App/assets/114975543/ab48cdcb-6b78-4e18-93b2-dae3e9d87440

iOS: Native
https://github.com/Expensify/App/assets/114975543/a35314a5-b541-4d9f-a9cd-92ffa5d02428

iOS: mWeb Safari
https://github.com/Expensify/App/assets/114975543/5a6da3bd-b9ab-4b98-a321-e5f6b43aef4d

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/114975543/a636c9b2-7574-4afe-987b-a8b71ecb9ba4

MacOS: Desktop
https://github.com/Expensify/App/assets/114975543/9a808bee-63ab-447a-98e5-b6540ed43906

@tsa321 Probably you closed this PR by mistake?


use dynamical memory allocation to allow large, unbounded messages

This uses the proposed publisherParam.allowPayloadResize option (as true) to allow dynamic resizing of the serialized payloads and therefore allowing large unbounded message types by allow us to set m_typeSize to 0.
Closes #36.

Closing in favor of https://github.com/eProsima/ROS-RMW-Fast-RTPS-cpp/pull/51


Default argument for Node.prototype.all()

Just a tiny suggestion for convenience: When calling node.all() without arguments, simply return all nodes, i.e. treat it as if a function that alays returns true was passed.
The same goes for node.first() I guess.
This is by no means necessary, it just popped into my head after I intuitively expected node.all() to 'just work'.
And also thanks for this package, it's pretty awesome.

I agree that would be an improvement, I'll do it soon.
Thank you for the kind words and your suggestion!

Fixed in release v1.0.1. Commit 75158eefbf1ffa0e14dbfab807b77ebd9ac5411a. Thanks!


make title text clickable

handling of the panels is more intuitive

Thanks for the PR, will take a look asap.

thinking about it again, the most intuitive solution would be to make the whole title bar clickable..

I implemented that now: a clickthe whole titlebar toggles the content visibility.
@ymcatar can you please have a look at this and the other two pull requests?


riscv64: Cleanup trap handling

👋 Hey,
This PR cleans up our trap instructions in the backend. We have 2 "TrapIf" style instructions. One that compares against zero, and a second that does any integer comparison. This PR does a couple of changes.
Merge both TrapIf and TrapIfC. The new TrapIf instruction allows trapping with any integer condition. This is the first commit, and it does not change any of the emitted instruction sequences, just our printing.
Use the new MachBuffer::defer_trap (#6011) method to place trap opcodes out of line. This does actually change the golden tests, and is contained to the second commit.
Lastly, the defer_trap change exposed a bug in our lowering of br_table. Previously we were emitting islands right before the jump table targets, but crucially after calculating the jump offset. This meant that if the island were actually emitted, we could jump right into the middle of it!
This was exposed by the defer_trap change since the test case would emit a trap before a huge br_table, forcing the island, and then jump into the first br_table target, which actually ended up being the trap opcode instead of the intended branch target.
We now emit the island at the start of the br_table sequence instead of in the middle.

Looks like on the test filetests/filetests/runtests/issue5569.clif we have a single block that produces about 8KiB of code, and the branch that we use for these traps only has a range of +/-4KiB, so we run into this assert.
I thought we would emit islands in the middle of a block if we needed to, but that appears not to be the case. I'm also not sure what the best solution here is, checking if we need an island at every instruction seems quite heavy handed.
This is also going to get worse when I introduced compressed conditional branches that only have +/- 256 bytes of range.

Ah yes you're right that islands are emitted once per block which is based on I::worst_case_size(). Is  this perhaps a case where the worse_case_size for RISC-V isn't accurate? Or perhaps the block is so large that a jump in the middle of the block can't jump out of the block?

This is also going to get worse when I introduced compressed conditional branches that only have +/- 256 bytes of range.

This may not actually work well with Wasmtime today unfortunately. As I'm sure you've seen we aren't guaranteed to know the branch target at emission time meaning that we can't use the current scheme you have for compressed instructions. It's technically possible to do it sort of but it means that it could make things worse since a 256 byte jump would run the risk of often requiring a veneer to a larger jump which means that what could have been a single jump would be veneer'd to two jumps.
When I was reading over the RISC-V documentation and intro and such I got the impression that the intention of the compressed instructions was to do what you've design today which is to emit everything and then compress it all after-the fact. The linker, however, seemed like it would be the one responsible for compressing RISC-V jumps which I'm not sure MachBuffer is positioned to do today. (e.g. MachBuffer isn't able to implement linker relaxation where all relocations are compressed to their smallest size). Not to say we couldn't ever implement it though, it's probably a chunk of work though.

Chiming in as well on branch ranges to say: two basic design tenets of MachBuffer's approach were:

We only emit islands between blocks, where we don't need to munge control flow to jump around them (on some backends then, e.g. aarch64, we do it for inline br_table tables too, since they're unbounded-ish, but that's morally "between blocks" as well even though it's within a pseudoinst)
We never backpatch code in a way that can expand size, because this requires a fixpoint loop in the limit and that could degrade to be very slow (imagine expanding a compressed jump to jump pushes a bunch of other branches out of range)

The former should be possible to relax, since the do-we-need-an-island check is cheap (just a compare to a deadline). We'd need to generate a jump beforehand that jumps around the island (and that jump should be longer-range!) If it actually happens it could be pretty undesirable from a performance standpoint -- the extra jump and break in fetch bandwidth could hurt in an inner loop -- so we'd want to do it only rarely (i.e., not optimistically pick the 256-byte-range jumps).
That should handle the long-basic-blocks problem re: 4K-range branches. It seems like the right way to handle the compressed-jump question is indeed a relaxation/shrinkage approach (which can't push other branches of out range, so you can do it without a fixpoint, but you might want to because other branches might become shrinkable too), but probably as a post-pass on the machine code. We'd need to keep all label fixups around to enable that as well. Maybe best to defer to a linker in e.g. Cranelift-as-AOT-rustc-backend cases, and omit this where compile times are more important (Cranelift-in-Wasmtime).

Ah yes you're right that islands are emitted once per block which is based on I::worst_case_size(). Is this perhaps a case where the worse_case_size for RISC-V isn't accurate? Or perhaps the block is so large that a jump in the middle of the block can't jump out of the block?

As far as I can tell worst_case_size is fairly accurate, It's currently at 124 bytes. The test for it points to the maximum being 116, so it's not too far off.
The block being too large seems to me the likely cause. The logs show that the full block is 8KiB, and we have a TrapIf about 1KiB into the block. That means that the closest island is 7KiB away, and the CondBr Instruction can't reach that.
I think I'm going to back out of the deferred_trap portion of this PR and land that separately, since it looks like we might need to make some changes to island checking for that to work properly with our limited branch range.

The linker, however, seemed like it would be the one responsible for compressing RISC-V jumps which I'm not sure MachBuffer is positioned to do today.

Maybe best to defer to a linker in e.g. Cranelift-as-AOT-rustc-backend cases, and omit this where compile times are more important (Cranelift-in-Wasmtime).

Yeah, I agree with that. I'm not sure I want to go full relaxation on MachBuffer yet, but a good middle ground would probably be expose all label usages as unresolved relocations, and let the external linker deal with it.


perform algorithms md analysis on and place results in a jupyter notebook

Results should follow guidelines HERE:
https://github.com/neurodata/checklists/blob/master/algorithms.md
jupyter notebook should be created in the tests folder

BRANDON: otsu vox and plos pipeline
WILL: connectedComponents and SLIC

See weekly goals for 1/16


bug: Long messages are not filtered and moved to a split

Did you check docs and existing issues?

[X] I have read all the noice.nvim docs
[X] I have searched the existing issues of noice.nvim
[X] I have searched the exsiting issues of plugins related to this issue

Neovim version (nvim -v)
0.8.1
Operating system/version
MacOS 13.1
Describe the bug
Either filtering on messages line height do not work, or routing a notification to a split do not work
Steps To Reproduce

launch the repro script
launch the :NoiceConfig command
a popup appears instead of a split

Expected Behavior
Long message content should go to a split
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
    vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
    vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
    "folke/tokyonight.nvim",
    "folke/noice.nvim",
    'MunifTanjim/nui.nvim',
    'rcarriga/nvim-notify'
    -- add any other plugins here
}
require("lazy").setup(plugins, {
    root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

require("noice").setup({
    lsp = {
        -- override markdown rendering so that **cmp** and other plugins use **Treesitter**
        override = {
            ["vim.lsp.util.convert_input_to_markdown_lines"] = true,
            ["vim.lsp.util.stylize_markdown"] = true,
            ["cmp.entry.get_documentation"] = true,
        },
    },
    presets = {
        bottom_search = false,
        command_palette = true, -- position the cmdline and popupmenu together
        long_message_to_split = true, -- long messages will be sent to a split
        inc_rename = false, -- enables an input dialog for inc-rename.nvim
        lsp_doc_border = false, -- add a border to hover docs and signature help
    },
    routes = {
        -- hidden "written" messages
        {
            filter = {
                event = "msg_show",
                kind = "",
                find = "written",
            },
            opts = { skip = true },
        },
        -- try to route noice config to split
        {
            filter = {
                event = "msg_show",
                min_height = 20,
                --cmdline = ":NoiceConfig",
            },
            view = "split",
        },
    },
})

Fixed it ; the example from the readme is wrong, you need to set a filter only on minwidth.


Add clarinet version, more faqs

Description
This PR

adds the required version of clarinet (1.8.0+)
adds more FAQs
fixes #95

Type of Change
Docs for sBTC DR 0.1

This does not work anymore with the new layout proposed in #101

Maybe we want to move the testnet page somewhere else. This should not be merged with the new structure


Add binary support

So, we can receive & send binary requests.
A cool example would be saving a file to the disk & render some texture into a render target.

I'd be keen to see this too


403 Forbidden on createFeedDocument

aws-tokens is generating successfully means i am authentication from aws but when i call  createFeedDocument method it is giving following error can any one help what i am doing wrong.?
Fatal error: Uncaught GuzzleHttp\Exception\ClientException: Client error: `POST https://sellingpartnerapi-fe.amazon.com/feeds/2020-09-04/documents` resulted in a `403 Forbidden` response: { "errors": [ { "message": "Access to requested resource is denied.", "code": "Unauthorized", "det (truncated...)

I have the same issue, did you manage to figure out what the issue was?

I have the same issue, did you manage to figure out what the issue was?

@fossman83 @moslemparve Guys did you figured this out i am having same issue


Insane Amounts of XP EnderIO -1.7.10-<IP_ADDRESS>3_beta

When ever i manually put in any dusts to be smelted in the alloy smelter in furnace mode and then pick it up once it has smelted up - 3 ingots picked up == to 17 LEVELS.
XP gain increases the more ingots i pick up at in one go from the smelter
EDIT: Seems to be happening with any ore from thermal foundation even if it is directly smelted,

I ran into this and think I may have randomly stumbled upon... something.
XP from the Alloy Smelter has always been a bit wonky for me, but it seems like it either gave the correct amount, or absolutely nothing. However, smelting a stack of birch logs into charcoal gives me 32 levels consistently. I tried a number of things to work around it, but without luck.
This was only happening to me with a dedicated server. Single player worked as expected.
Then I noticed I was getting a debug message about the following in my OreDictionaryPreferences_User.xml file:
<preference oreDictionary="ingotAluminuim">
  <itemStack modID="TConstruct" itemName="materials" itemMeta="11" />
</preference>

It seems by correcting ingotAluminuim to ingotAluminium I get the same amount of XP from birch logs as smelting in a normal furnace.
I have absolutely no idea if this is the solution or a red herring (esp. since there are TONS of similar debug message about non-existent ore dictionary names from SAGMillRecipes_Core.xml) but I figure I'd mention it since it (seems to have) worked for me and it all shares the same base parsing code (although I realize OreDictionaryPreferenceParser is responsible for this and shouldn't effect vanilla smelting recipes.)
This is with EnderCore <IP_ADDRESS>_beta and EnderIO <IP_ADDRESS>1_beta.

@mmelvin0 Can you reproduce this again? Would you be willing to do so with a debugging version of Ender IO?

I'm positive I can reproduce it with the current (soon to be previous) version of my mod pack.
If you have a debugging version for me to try (I assume this means you have some ideas...) I'd be more than happy to try.
I already have an EnderIO dev environment set up from a while back. Was planning on stepping through the code later this week to see if anything jumps out at me, but your suggestion sounds like far less effort :)

Thank you very much! It is not that I have an idea, but I know the callstack that produces the XP. I just lined it with debug statements so we can get an idea where the wrong numbers get in.
http://loenwind.info/EnderIO-1.7.10-<IP_ADDRESS>1t0_beta.jar
The output in the logfile will look like this:
[04:05:26] [Client thread/INFO] [EnderIO]: ContainerAlloySmelter.decrStackSize(): par1=1, numResults=0, getStack().stackSize=1
[04:05:26] [Server thread/INFO] [EnderIO]: ContainerAlloySmelter.decrStackSize(): par1=1, numResults=0, getStack().stackSize=1
[04:05:26] [Server thread/INFO] [EnderIO]: VanillaSmeltingRecipe.getExperienceForOutput(): output=1xitem.coal@1, FurnaceRecipes.smelting().func_151398_b(output)=0.15, return=0.15
[04:05:26] [Server thread/INFO] [EnderIO]: AbstractPoweredTaskEntity.getExperienceForOutput(): output=1xitem.coal@1, lastCompletedRecipe=crazypants.enderio.machine.alloy.VanillaSmeltingRecipe@32746356, lastCompletedRecipe.getExperienceForOutput(output)=0.15
[04:05:26] [Server thread/INFO] [EnderIO]: VanillaSmeltingRecipe.getExperienceForOutput(): output=1xitem.coal@1, FurnaceRecipes.smelting().func_151398_b(output)=0.15, return=0.15
[04:05:26] [Server thread/INFO] [EnderIO]: ContainerAlloySmelter.onCrafting(): output=1xitem.coal@1, outputSized=1xitem.coal@1, XP=0.15

Three separate test runs, three separate results.
First time: expected XP results.
Second time: no XP.
Third time: 960 XP (e.g. 37 levels) for a 64 stack
Between each try I restarted the dedicated server and left the client running.
Here's the snippet from the server log for the third try:
[19:59:34] [Server thread/INFO] [EnderIO/]: ContainerAlloySmelter.decrStackSize(): par1=64, numResults=0, getStack().stackSize=64
[19:59:34] [Server thread/INFO] [EnderIO/]: VanillaSmeltingRecipe.getExperienceForOutput(): output=64xitem.coal@1, FurnaceRecipes.smelting().func_151398_b(output)=15.0, return=960.0
[19:59:34] [Server thread/INFO] [EnderIO/]: AbstractPoweredTaskEntity.getExperienceForOutput(): output=64xitem.coal@1, lastCompletedRecipe=crazypants.enderio.machine.alloy.VanillaSmeltingRecipe@a33956d, lastCompletedRecipe.getExperienceForOutput(output)=960.0
[19:59:34] [Server thread/INFO] [EnderIO/]: VanillaSmeltingRecipe.getExperienceForOutput(): output=64xitem.coal@1, FurnaceRecipes.smelting().func_151398_b(output)=15.0, return=960.0
[19:59:34] [Server thread/INFO] [EnderIO/]: ContainerAlloySmelter.onCrafting(): output=64xitem.coal@1, outputSized=64xitem.coal@1, XP=960.0

Here's the log of taking a half stack:
[20:01:46] [Server thread/INFO] [EnderIO/]: ContainerAlloySmelter.decrStackSize(): par1=32, numResults=0, getStack().stackSize=32
[20:01:46] [Server thread/INFO] [EnderIO/]: VanillaSmeltingRecipe.getExperienceForOutput(): output=32xitem.coal@1, FurnaceRecipes.smelting().func_151398_b(output)=15.0, return=480.0
[20:01:46] [Server thread/INFO] [EnderIO/]: AbstractPoweredTaskEntity.getExperienceForOutput(): output=32xitem.coal@1, lastCompletedRecipe=crazypants.enderio.machine.alloy.VanillaSmeltingRecipe@a33956d, lastCompletedRecipe.getExperienceForOutput(output)=480.0
[20:01:46] [Server thread/INFO] [EnderIO/]: VanillaSmeltingRecipe.getExperienceForOutput(): output=32xitem.coal@1, FurnaceRecipes.smelting().func_151398_b(output)=15.0, return=480.0
[20:01:46] [Server thread/INFO] [EnderIO/]: ContainerAlloySmelter.onCrafting(): output=32xitem.coal@1, outputSized=32xitem.coal@1, XP=480.0

It seems to stay consistent while the server is running.
Seems to be (weird, since Thermal Expansion doesn't expose this behavior, despite giving XP from furnaces) either a vanilla bug or func_151398_b() isn't what you think it is.
Here's the full server log from the third run: https://gist.githubusercontent.com/mmelvin0/fd154d99455ff6a03ed8/raw/5220e5fa8df4aa1fb8025fa099566dcf483dd80b/fml-server-latest.log

Also of note is the "correct" run returned 0.1 XP per log, but that's not correct, it's 0.15 (as per FuranceRecipes.java from the Minecraft Force source.)
[19:46:02] [Server thread/INFO] [EnderIO/]: ContainerAlloySmelter.decrStackSize(): par1=64, numResults=0, getStack().stackSize=64
[19:46:02] [Server thread/INFO] [EnderIO/]: VanillaSmeltingRecipe.getExperienceForOutput(): output=64xitem.coal@1, FurnaceRecipes.smelting().func_151398_b(output)=0.1, return=6.4
[19:46:02] [Server thread/INFO] [EnderIO/]: AbstractPoweredTaskEntity.getExperienceForOutput(): output=64xitem.coal@1, lastCompletedRecipe=crazypants.enderio.machine.alloy.VanillaSmeltingRecipe@6e884525, lastCompletedRecipe.getExperienceForOutput(output)=6.4
[19:46:02] [Server thread/INFO] [EnderIO/]: VanillaSmeltingRecipe.getExperienceForOutput(): output=64xitem.coal@1, FurnaceRecipes.smelting().func_151398_b(output)=0.1, return=6.4
[19:46:02] [Server thread/INFO] [EnderIO/]: ContainerAlloySmelter.onCrafting(): output=64xitem.coal@1, outputSized=64xitem.coal@1, XP=6.4

Yes. someone is messing with the vanilla class here. I'm not sure if it is just registering weird values or if actual patching is involved. I fear I have to add some code to dump the actual data store of it to see.

Turns out for me this is being caused by Biomes O' Plenty giving an XP value of 15.0F instead of 0.15F to logs -> charcoal.
See also Glitchfiend/BiomesOPlenty#564


get_pushes

Hi
The client on python has functions to GET information such as get_pushes.
There is nothing develop on this go module to perform such operations, right?
BR
J

Hey,
That is correct. Also I'm no longer actively maintaining this project, though forks / pull requests are welcome.


Sql aggregate functions

Added the aggregation funciton of #9

Need to update the round function as it just nonsense.


Custom webpack loader not working

Hey!
If i use a custom webpack loader loader it works in storybook but not in creevy
import {stuff} from '!./myloader!./myfile-to-be-custom-loaded';

in creevy i get this console output
Cannot find module '!./myloader!./myfile-to-be-custom-loaded'

in storybook it works just fine.
Does creevy use the webpack config from storybook?
This case is actually even simpler since i explicitly invoke the loader so this does not even need the webpack config.
I also tried with absolute paths to avoid any issues with that. No success.
Any ideas?
Thank you!

Update:
Also tried with webpack resourceQueries:
Works in storybook dev mode.
but not in creevey
Error: Cannot find module '../src/myfile-to-be-custom-loaded.js?my-loader'

Also, I noticed the same error is produced when doing a static storybook build.
However, the bundling goes through and the bundle works.
are there different webpack stacks used during preview/build/creevy?

Hi @sijakret. I'm sorry for the bad experience with Creevey.
For Storybook 6.2+ Creevey uses a different way to load stories metadata through babel by default. It was done to support other bundlers, like Vite. You can try to define useWebpackToExtractTests: true in your Creevey config. This flag forces to use old fashion way to load stories metadata by using webpack, so I hope it should work with custom loaders.
If it doesn't help, I'll suggest to wait a little. Currently, I work on supporting CSFv3 and the new tests format, where no more is needed to load metadata by using babel or webpack.


Document with same document id can't be replaced

When I add the document with same id but different content to the index, the former still can be searched.
Maybe it should be replaced by the latter.

Let me think about it, may not be allowed to repeat id.

If I use riot as a search engine of customer support tickets system,each ticket can be treated as a document, and ticket id equals document id.When the ticket is edited by user, I will update the document, but if the document can't be replaced, those documents  are redundant.

Ok, i see, let me think about it and improve it.

You can RemoveDoc first then IndexDoc, let me think about how to do better.

OK


[Checkpoint Executor] Make a per-epoch component

Make CheckpointExecutor exit after it reaches end of epoch
Enforce the invariant that clean exit can only happen if we reach end of epoch (this means we now panic if the statesync channel is closed, rather than exit gracefully)
Move end of epoch send channel to SuiNode, which will alert all listeners once CheckpointExecutor exits
Fix TransactionOrchestrator to subscribe to SuiNode end of epoch channel, which we are guaranteed should never close

Just double check, you are still iterating on this PR, right?

@lxfind yeah I was still iterating. It's now ready for another review though pelase


add external-dns flags to CI install make target

Follow up to https://github.com/openshift/hypershift/pull/1149
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/hold
I think there is a potential issue here with external-dns running concurrently in different jobs deleting one another's records.

/hold cancel


added year to the license file

added year as 2017-present in license file

We were guided not to add a year. That's our plan for the file unless we find out it prevents someone from using the product.


Ideas for lessons

Testing workflows with small versions of test data
On basics of Docker
A full one on linting
A full one on typing
Package management best practices for R

Intro to R
Intro to python
Package management/development in python (pip and PyPI) - this might be more legwork because (from what I've found) there aren't as good and concise resources for this as there are for R packages

After we run Intro to Python, it could be fun to cover things like pandas, matplotlib, plotly, etc. in greater depth! I'd be happy to help with those. I personally could also benefit from a ggplot tutorial...
I think having package development workshops for both Python and R would be super helpful - perhaps we could even come up with a standard template for folks to start with? I've been pulling together info from random web resources...

After we run Intro to Python, it could be fun to cover things like pandas, matplotlib, plotly, etc. in greater depth! I'd be happy to help with those.

I love those ideas!

I personally could also benefit from a ggplot tutorial...

I don't even think i can count the number of times i've taught ggplot. I'm more than happy to do it again. do you think we need an intro to R series like python in order to do an intro to ggplot, or if I cover how to read in a CSV is that enough? there is some stuff with ggplot (like data should be in long format most of the time), but a lot of times you can get the plot you want without it.

I think having package development workshops for both Python and R would be super helpful - perhaps we could even come up with a standard template for folks to start with? I've been pulling together info from random web resources...

Great idea. For sourmashconsumr, I used on website basically exclusively (https://r-pkgs.org/)...I guess there isn't something similar for python?

[ ] Emily requested one on interactive data viz

+1 to discussing Docker basics, I'm trying to figure it out and it's hard to know where to begin


navbar for mobile and tab and welcome page

Hello,
I wanted to add the navbar for the tab and mobile version because theirs a vertical navbar on the pc version so that i have modified for the tab version and navbar version
i have maked whole welcome page responsive for the tab mobile and pc
pc version

tab version

mobile version

@4darsh-Dev  kindly assign it as a level 3 under gssoc i have done coding i will push it as you assign it to me !!

assigned to you @anurag6569201
have a look on contributing.md before raising the pr

Hey @anurag6569201 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


GGMLv3 support

This PR pins llama-cpp-python in the Docker image to 0.1.54 so newer models like Guanaco work. This breaks compatibility for GGMLv2 models (a decision made by llama.cpp developers). It may be a good idea to keep a branch of Serge that supports GGMLv2.

this will need to update the README file for the new models docs

Pending https://github.com/nsarrazin/serge/pull/336


Prevent CDN/domain service provision from breaking on duplicate parameters

It should be possible to create an instance with the same parameters in another space without breaking the broker state or the existing instance.
Acceptance Criteria

[ ] GIVEN I have a CDN/Cloudfront service instance for domain X in Space A WHEN I create a new instance with the same domain in Space B, THEN the service is cleanly created or not-created.

@bengerman13 previously said:

Since this currently causes a user's service instance to break and requires someone from cloud.gov to intervene to fix it, we should either support it or prevent it, whether or not such moves are necessary.

obsoleted by new broker


Improve --data-split-num (minor tweak of #19)

Minor tweak of https://github.com/hqucms/weaver-core/pull/19.

When input dataset is in Parquet format, the entire file must be first read into the memory and then select events from start_entry:stop_entry. This makes --fetch-step 0.01 still requires loading all datasets into the memory.
A simple solution to efficiently read Parquet dataset, without affecting the exiting function is to use --fetch-step 1 --data-split-num 100 (recently added to weaver) instead of  --fetch-step 0.01. Therefore, this PR improves --data-split-num by handle the split in separate input groups, and allowing it to split more evenly.
For example, input datasets are separated into groups process_1: filelist_1, process_2:filelist_2, …. Now,

--data-split-num split data separately in each group so that the mixing is even among the groups.
In each group, --data-split-num can handle the case if N(file) is not divisible by the split number. Say, for N=5 and split_num=3, in the case of load_range=(0, 0.1), we have

iter1: load file 0, 1; load_ranges=[(0, 0.1), (0, 0.0667)]
iter2: load file 1, 2, 3; load_ranges=[(0.0667, 0.1), (0, 0.1), (0, 0.0333)]
iter3: load file 3, 4; load_ranges=[(0.0333, 0.1), (0, 0.1)]

The initial impl. of --data-split-num (achieved inside the function _load_next) has been reverted.

Thanks a lot! A minor optimization has been implemented to improve performance by reordering the two for loops. Previously, n_div_d_sep_array was computed in the inner loop, which could be inefficient when the number of splits is large.
ref: https://github.com/colizz/weaver-core/commit/7c8d9230630f72fb640e041ad59c0bb5c103305b

Here is a safety check of this functionality (from the debug output):
Iter 0:
  - ./datasets/JetClassII/Pythia/Res34P_0350.parquet with load_range=(0.0, 0.86)
  - ./datasets/JetClassII/Pythia/Res2P_0065.parquet with load_range=(0.0, 0.2)
  - ./datasets/JetClassII/Pythia/QCD_0185.parquet with load_range=(0.0, 0.28)
Iter 1:
  - ./datasets/JetClassII/Pythia/Res34P_0350.parquet with load_range=(0.86, 1.0)
  - ./datasets/JetClassII/Pythia/Res34P_0605.parquet with load_range=(0.0, 0.72)
  - ./datasets/JetClassII/Pythia/Res2P_0065.parquet with load_range=(0.2, 0.4)
  - ./datasets/JetClassII/Pythia/QCD_0185.parquet with load_range=(0.28, 0.56)
Iter 2:
  - ./datasets/JetClassII/Pythia/Res34P_0605.parquet with load_range=(0.72, 1.0)
  - ./datasets/JetClassII/Pythia/Res34P_0055.parquet with load_range=(0.0, 0.58)
  - ./datasets/JetClassII/Pythia/Res2P_0065.parquet with load_range=(0.4, 0.6)
  - ./datasets/JetClassII/Pythia/QCD_0185.parquet with load_range=(0.56, 0.84)
Iter 3:
  - ./datasets/JetClassII/Pythia/Res34P_0055.parquet with load_range=(0.58, 1.0)
  - ./datasets/JetClassII/Pythia/Res34P_0845.parquet with load_range=(0.0, 0.44)
  - ./datasets/JetClassII/Pythia/Res2P_0065.parquet with load_range=(0.6, 0.8)
  - ./datasets/JetClassII/Pythia/QCD_0185.parquet with load_range=(0.84, 1.0)
  - ./datasets/JetClassII/Pythia/QCD_0075.parquet with load_range=(0.0, 0.12)
Iter 4:
  - ./datasets/JetClassII/Pythia/Res34P_0845.parquet with load_range=(0.44, 1.0)
  - ./datasets/JetClassII/Pythia/Res34P_0750.parquet with load_range=(0.0, 0.3)
  - ./datasets/JetClassII/Pythia/Res2P_0065.parquet with load_range=(0.8, 1.0)
  - ./datasets/JetClassII/Pythia/QCD_0075.parquet with load_range=(0.12, 0.4)
Iter 5:
  - ./datasets/JetClassII/Pythia/Res34P_0750.parquet with load_range=(0.3, 1.0)
  - ./datasets/JetClassII/Pythia/Res34P_0810.parquet with load_range=(0.0, 0.16)
  - ./datasets/JetClassII/Pythia/Res2P_0070.parquet with load_range=(0.0, 0.2)
  - ./datasets/JetClassII/Pythia/QCD_0075.parquet with load_range=(0.4, 0.68)
Iter 6:
  - ./datasets/JetClassII/Pythia/Res34P_0810.parquet with load_range=(0.16, 1.0)
  - ./datasets/JetClassII/Pythia/Res34P_0025.parquet with load_range=(0.0, 0.02)
  - ./datasets/JetClassII/Pythia/Res2P_0070.parquet with load_range=(0.2, 0.4)
  - ./datasets/JetClassII/Pythia/QCD_0075.parquet with load_range=(0.68, 0.96)

Thanks a lot! A minor optimization has been implemented to improve performance by reordering the two for loops. Previously, n_div_d_sep_array was computed in the inner loop, which could be inefficient when the number of splits is large. ref: colizz@7c8d923

Thanks a lot @colizz ! I cherry-picked the commit and pushed it to dev/custom_train_eval.


An error occured while starting <IP_ADDRESS>-ee image

Hello.
I was able to create an image for <IP_ADDRESS>-ee.
I was also able to deploy it on Google Kuberentes engine. (all things as expected)
Now, i'm trying to deploy it on Opnshift Container Platform on-prem, I got this error:
The listener supports no services
The command completed successfully
cat: /opt/oracle/cfgtoollogs/dbca/ORCLDB/ORCLDB.log: No such file or directory
cat: /opt/oracle/cfgtoollogs/dbca/ORCLDB.log: No such file or directory
mv: cannot stat '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/dbs/spfileORCLDB.ora': No such file or directory
mv: cannot stat '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/dbs/orapwORCLDB': No such file or directory
mv: cannot stat '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/tnsnames.ora': No such file or directory
ORACLE_HOME = [/home/oracle] ? ORACLE_BASE environment variable is not being set since this
information is not available for the current user ID .
You can set ORACLE_BASE manually if it is required.
Resetting ORACLE_BASE to its previous value or ORACLE_HOME
The Oracle base remains unchanged with value /opt/oracle
/opt/oracle/checkDBStatus.sh: line 26: sqlplus: command not found
#####################################
########### E R R O R ###############
DATABASE SETUP WAS NOT SUCCESSFUL!
Please check output for further info!
########### E R R O R ###############
#####################################
The following output is now a tail of the alert.log:
tail: cannot open '/opt/oracle/diag/rdbms/*/*/trace/alert*.log' for reading: No such file or directory
tail: no files remaining

I have already assign a Security Context Constraints anyuid to the service account default to be able to run as any user (oc adm policy add-scc-to-user anyuid -z default)

Can you please share the entire output as well as the docker run command and parameters you have used?

Hallo Grald,
thank you a lot for the answer.
I'm deploying the oracle container using a deployment file. I have already run it using docker run .... and it works fine.
I deployed the same yaml file in Google Kubernetes Engine and it works fine.
The logs and the deployment yaml files are below.
As i said before, i have already assign a Security Context Constraints anyuid to the service account default to be able to run as any user (oc adm policy add-scc-to-user anyuid -z default)
logs.txt
deployment.txt

Thanks for the additional info, @hichem-belhocine.
This looks very much like a configuration issue within Open Shift. I suppose we already knew that much, given that it works fine on GKE and via docker run. :)
It looks like the container isn't allowed/able to start updbca. The failure below:
LSNRCTL for Linux: Version <IP_ADDRESS>.0 - Production on 14-MAY-2020 08:15:43

Copyright (c) 1991, 2014, Oracle.  All rights reserved.

Starting /opt/oracle/product/<IP_ADDRESS>/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
System parameter file is /opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/listener.ora
Log messages written to /opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
Start Date                14-MAY-2020 08:15:43
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/listener.ora
Listener Log File         /opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/log/listener.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))
The listener supports no services
The command completed successfully
cat: /opt/oracle/cfgtoollogs/dbca/ORCLDB/ORCLDB.log: No such file or directory
cat: /opt/oracle/cfgtoollogs/dbca/ORCLDB.log: No such file or directory

is from this piece of code:
lsnrctl start &&
dbca -silent -responseFile $ORACLE_BASE/dbca.rsp ||
 cat /opt/oracle/cfgtoollogs/dbca/$ORACLE_SID/$ORACLE_SID.log ||
 cat /opt/oracle/cfgtoollogs/dbca/$ORACLE_SID.log

lsnrctl start works successfully, but dbca -silient ... fails which causes the two outputs from cat above.
Now the question is, why is dbca not begin run on Open Shift? :)

I have tested this example: https://medium.com/@pittar/running-oracle-12c-on-openshift-container-platform-ca471a9f7057
It works fine, but i need to run the <IP_ADDRESS>-ee version.

I'm trying to debug this problem for @hichem-belhocine on his test-cluster. How can I get more informations regarding dbca? I have no clue about oracle but am familiar with containers ;)
I just found out, that dbca is exiting with exitcode 1 instead of 0 but the command throws no error message.

Hi @gvenzl,
I would tell you that i have created the 12.2.01 image and it works fine.
Thank you.
Best regards.


"Cannot read property 'substring' of undefined" using elm + elm-format

VSCode Version: 1.8.1
OS Version: MacOS 10.12.1

Steps to Reproduce:

Install/configure plugins: elm, elm-format
attempt to format Elm code.

Result is Error Cannot read property 'substring' of undefined
This is not reproducible in VSCode Version: 1.9.0-insider.

Since it's an extension issue, I'll suggest to file issues in extensions' repositories and start investigation there. Thanks!


Update minimal nodejs version to 4.2.

As of Protractor 3.0.0 any NodeJs version lower than 4.2 will not work anymore
see https://github.com/angular/protractor/blob/master/CHANGELOG.md#300
This pull request will also update the other dependencies.

+1


Turn tests.yaml into a list of tests

This should allow tests to be repeatable, which is a feature seeked needed in the multi host use cases.

yq is not installed, new dependency?

yq is not installed, new test dependency?

Yes, see https://github.com/teemtee/tmt/pull/1854

yq is not installed, new test dependency?

Yes, see #1854

This is #1854?

yq is not installed, new test dependency?

Yes, see #1854

This is #1854?

Dammit! I meant https://github.com/teemtee/tmt/pull/1849

@psss consider this one for 1.22, it'd push the multi-host support a bit further again


Add l4 load balancer test

Summary

Add test for l4 load balancer.
Fixed a bug in which adding and deleting ports at the same time would not be processed.

5485f5ed10523f26145636ad52c40a9442c6a170

Review

[x] CI is successful.

LGTM


[FALSE-POSITIVE]

Domains or links
Please list any domains and links listed here which you believe are a false positive.
https://frau-z-macht-das.de/
More Information
How did you discover your web site or domain was listed here?
Imunify360 alarm
Have you requested removal from other sources?
Yes, BitDefender, CyRadar, Fortinet, G-DATA, Sophos, VIPRE, Webroot.
The domain was removed as it was a false positive listing.
Additional context
Add any other context about the problem here.
:exclamation:
We understand being listed on a Phishing Database like this can be frustrating and embarrassing for many web site owners. The first step is to remain calm. The second step is to rest assured one of our maintainers will address your issue as soon as possible. Please make sure you have provided as much information as possible to help speed up the process.
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR to mitchellkrogza/phishing repository, on the falsepositive.list file

https://github.com/mitchellkrogza/phishing/blob/main/falsepositive.list
Please include the same above information to help speed up the whitelisting process.

Not showing as listed by us
https://www.virustotal.com/gui/domain/frau-z-macht-das.de

But we still see the entries in your current database:
https://github.com/mitchellkrogza/Phishing.Database/blob/master/ALL-phishing-links.txt
Entries:
https://frau-z-macht-das.de/sign/wia
https://frau-z-macht-das.de/sign/wia/2.html
https://frau-z-macht-das.de/sign/wia/3.html
https://frau-z-macht-das.de/sign/wia/4.html
Those are all 404 links. Please remove them from your list. Thanks in advance!

Where are they listed on that file??
wget -O- "https://raw.githubusercontent.com/mitchellkrogza/Phishing.Database/master/ALL-phishing-links.txt" | grep -i "imunify360.alarm"
--2024-06-24 18:39:53--  https://raw.githubusercontent.com/mitchellkrogza/Phishing.Database/master/ALL-phishing-links.txt
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 90670018 (86M) [text/plain]
Saving to: ‘STDOUT’

                                                     100%[========================================================================================================================================>]  86,47M  2,50MB/s    in 21s

2024-06-24 18:40:14 (4,15 MB/s) - written to stdout [90670018/90670018]

Search result from External Hosts-Sources
@mypdns's External Hosts-Sources can be found here

Sorted result

Search result from easylist

Search in Matrix
Search results from Matrix blacklist project

Did not find any matching RPZ records
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Thanks to My Privacy DNS for this knowledge
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Drilling for imunify360.alarm

@spirillen
The four links mentioned are on lines 731.370 till 731.370.
You can us the following command to see them:
wget -O- "https://raw.githubusercontent.com/mitchellkrogza/Phishing.Database/master/ALL-phishing-links.txt" | grep -i "frau-z-macht-das\.de"

--2024-06-25 05:42:09--  https://raw.githubusercontent.com/mitchellkrogza/Phishing.Database/master/ALL-phishing-links.txt
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 2606:50c0:8001::154, 2606:50c0:8002::154, 2606:50c0:8000::154, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8001::154|:443... connected.
HTTP request sent, awaiting response... 200 OK
https://frau-z-macht-das.de/sign/wia
https://frau-z-macht-das.de/sign/wia/2.html
https://frau-z-macht-das.de/sign/wia/3.html
https://frau-z-macht-das.de/sign/wia/4.html

Thanks in advance for the removal of them!

AAhh, I've been reading the wrong line...

@mitchellkrogza As the topic is closed already, shall I open a new issue for the delisting of the 4 links?

@DATA-HORIZON
In case you remove the links from the #walledgarden I can help you in https://github.com/mitchellkrogza/Phishing but I need to be able to access them from a public network an not only the walledGarden by the #Big5 as that is 100% blacklisted in my NFTables firewall by IP addresses.

@spirillen The #walledgarden has been disabled for the domain. Please give it a new try. Thanks in advance!

@DATA-HORIZON Super, keep it that way, that will improve the number who can access your site, as CF are very very very keen and big fan of censuring the internet.
Open a issue as mentioned above and I merge it


Alias key and sleep to actions

The custom parses for key and sleep actions should also use the field action_name to address "key" and "sleep", which should also be aliases as identifiers. Furthermore, the field arguments should generally not include the parentheses.

Closing as a duplicate of #21.


GH-37606: [C++][Parquet] Support user memory pool in Dataset Parquet writer

Rationale for this change

Support user memory pool in Dataset Parquet writer
What changes are included in this PR?

2lines tiny update
Are these changes tested?

no
Are there any user-facing changes?
no

Closes: #37606

I'll later draft a new patch for this


Please update README.md // installation

Hi,
The command
npm install -g epubconverter
does not work as specified in the git repo.
Please update.
Kind Regards!

x2


shell surface interface

Add stubs for the wl_shell_surface interface.
Implement wl_shell_get_shell_surface by creating the shell surface and settings
its implementation to these stubs.

LGTM so far

I implemented the xdg toplevel stubs. It's getting really messy.
I think the new goal of the PR is going to be to get weston-simple-shm to work correctly and this is part of that. Currently it crashes wlroots. Then we can move on to toolkits.

This is enough of the xdg-shell interface to get weston-simple-shm to show a single buffer. And by that, I mean it only shows one buffer. I hope the next buffer is a little easier.
It's ugly and it has memory leaks but I don't want to focus on cleaning it up right now because my big picture goal is to get GTK (or another toolkit) to give me a buffer and for that it will be necessary to work on the surface interface fleshing out surface_attach, surface_damage, and surface_commit.
So I think this is ready to merge.

Why is it necessary to jump all the way to GTK? weston-simple-shm uses damage and commit too. I don't really feel comfortable merging something "ugly" with known memory leaks. Baby steps.

My reasoning is that the only way to clean this up properly is to understand how the toolkits actually use it which is done most efficiently by reverse engineering. weston-simple-shm only uses a very small part of the shell interface so it doesn't serve as a good model for how a client in the wild will behave. Once we can see how an application like gnome-calculator uses the interface, it will be much easier to work on this. But for that to happen, I think there is another interface that needs to be implemented. I'm trying to figure out what that is now.

gnome-calculator probably needs wl_seat and friends to make any changes appear on its buffers. I understand that weston-simple-shm isn't going to get us far with respect to wl_shell - but that's a feature, not a bug. I want to focus first on getting wl_surface and wl_buffer completely fleshed out first.

Yeah I agree.
My plan is to do a complete implementation of wl_surface and wl_buffer now, then move onto wl_seat, and then we can come back to this after we have a high level understanding of how all the components interact with each other.

how about that for the meson protocol build?

Thanks!


fix "Cancel" links in IoSetCancelRoutine

These docs should link to DRIVER_CANCEL and not IPrinterExtensionRequest::Cancel

Thanks for the eagle eye @wumb0!  Appreciate the PR.


Integrate flash.sh from RteCtrl

For more inf.:
https://github.com/3mdeb/RteCtrl/pull/22
https://github.com/3mdeb/meta-rte/issues/80

Thank you for your feedback. Fixed here ffda8494ae55d154bccfa9d3415e6767edc6ea2b.

This script will be available in the future releases of RTE OS image


FlatList scrollToIndex() dont work without specifying the getItemLayout prop

React native version 0.45.1

Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information, or the list of reproduction steps is not complete. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!

No problem I will reproduce the error in a clean project. Thank you


No immediate notification that side-loaded extension was successfully installed.

VSCode Version: 1.3.1
OS Version: 10.11.3

Side-loading an extension through the File -> Open interface does not show any notification in the interface that installation was successful. Only the extensions tab shows that the installation was successful.
Steps to Reproduce:

Select File - Open
Select a .vsix file in the file picker
Observe that the interface does not show any notification.

Gif of me installing a side loaded extension, KiteCode:

Duplicate of #8075


Gekko can't find the strategy

it seems that backtestTool can't find  my strategy. Strategy is in /strategies folder and toml is in \config\strategies. Below details of the the output. Same behavior in win10 and ubuntu. Not sure why this is happening, other strategies like RSI, RSI_BULL_BEAR .... are working fine.
Any advice?
#output:
============================================================= L A S T    R E S U L T S ============================================================
Pair                                      Strategy       Profit   Profit-market  Trades/day  Win trades  Best win  Worst loss    HODL  Days   Time

USDT-BTC Backtest is failed. Gekko can't find the strategy "GbtEmaRsiV02"
[2018-09-14 20:53:10] 100% complete. Elapsed: 00:00:00, average backtest duration: 00:00

it seems that solution for "can't find the strategy"  is renaming strategy and toml file to all capital letters file name like "ABC".
I don't know if this is a bug, expected behavior, or my mistake because now i get messages like:
===================================================================================================================================================
[2018-09-15 21:14:40] 6 backtests remain
============================================================= L A S T    R E S U L T S ============================================================
Pair                                      Strategy       Profit   Profit-market  Trades/day  Win trades  Best win  Worst loss    HODL  Days   Time

Month '16' out of range 0..11 at backtest.pl line 330.
Can't use an undefined value as a HASH reference at backtest.pl line 674.
Month '16' out of range 0..11 at backtest.pl line 330.
Month '16' out of range 0..11 at backtest.pl line 330.
Month '16' out of range 0..11 at backtest.pl line 330.
Month '16' out of range 0..11 at backtest.pl line 330.
any ideas about this one?


I got an error when i run ppo and trpo....

I typed ' python3 run_atari.py' to run it, and this error came up:
Traceback (most recent call last):
File "run_atari.py", line 55, in
main()
File "run_atari.py", line 52, in main
train('PongNoFrameskip-v4', num_timesteps=40e6, seed=0, num_cpu=8)
File "run_atari.py", line 26, in train
logger.session().enter()
TypeError: init() missing 1 required positional argument: 'dir'
Traceback (most recent call last):
File "run_atari.py", line 55, in
main()
File "run_atari.py", line 52, in main
train('PongNoFrameskip-v4', num_timesteps=40e6, seed=0, num_cpu=8)
File "run_atari.py", line 26, in train
logger.session().enter()
TypeError: init() missing 1 required positional argument: 'dir'

Primary job  terminated normally, but 1 process returned
a non-zero exit code.. Per user-direction, the job has been aborted.

mpirun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:
Process name: [[51768,1],0]
Exit code:    1
Traceback (most recent call last):
File "run_atari.py", line 55, in
main()
File "run_atari.py", line 52, in main
train('PongNoFrameskip-v4', num_timesteps=40e6, seed=0, num_cpu=8)
File "run_atari.py", line 21, in train
whoami  = mpi_fork(num_cpu)
File "/home/wonchul/Desktop/baselines-master/baselines/pposgd/mpi_fork.py", line 20, in mpi_fork
subprocess.check_call(args, env=env)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['mpirun', '-np', '8', '/usr/bin/python3', 'run_atari.py']' returned non-zero exit status 1
Do i have to add something with 'python3 run_atari.py' ?
Or is there any problem....?
Could you help me????

@wonchul-kim Hi, have you solved this problem? How to fix it? THX

I just moved the all dependent files to the related folder
2017-08-02 19:09 GMT+09:00 Jackie Tseng<EMAIL_ADDRESS>
@wonchul-kim https://github.com/wonchul-kim Hi, have you solved this
problem? How to fix it? THX
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openai/baselines/issues/80#issuecomment-319629591,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT7jwf_eB-9_OAXb7SQ9OYHcxUfhxlwNks5sUErggaJpZM4Onuph
.


No native build was found, react native

Hello, I want to use hyperswarm in android (I know, that is weird).
I have rn-nodeify to supply node modules, but when I run the app Expo says "no native build was found for platform=android arch=javascript runtime=node abi=undefined uv= libc=glibc".
screenshot
More details:
Node version: v13.12.0
NPM version: 6.14.4
Expo version: 3.17.11
Hyperswarm version: 2.10.1

This issue is related to a confict between rn-nodeify and Expo.
I'll try to do it without Expo, I will post the result here.


You can now specify a pivot point for bending.

For example if the size of a bendable cuboid is 16 and you set the pivot value to 6 and the direction is UP it will bend a little higher up.
I tested this with player animator (I plan to use this for capes, PR for that coming soon.) and it seems to work just fine.
I also removed some stuff I saw as unnecessary such as the 3D skin layers compat that doesn't work.
I do plan to work on 3D skin layers compat + a lot A LOT more compat stuff but as a seperate mod rather than part of bendy-lib.

https://cdn.discordapp.com/attachments/1163186803176640583/1318160341263192074/2024-12-16_13-47-17.mp4?ex=67614ffb&is=675ffe7b&hm=e89e7d93a95ca2b75f9aadea409d921ff47fa27d7c8fdc19a2757f5612d6ee03&

Oh, and please publish this to your maven repository for the player animator PR 🙏


Support "Endless method definition" syntax for Ruby 2.8 (3.0)

This PR supports "Endless method definition" syntax for Ruby 2.8 (3.0).
Parser gem supports this syntax by https://github.com/whitequark/parser/pull/676.
Ref: https://bugs.ruby-lang.org/issues/16746

I think we should also add an endless? predicate to the node extension.

I commented in whitequark/parser#676 that I hope that we can get a simple def (and also in https://bugs.ruby-lang.org/issues/16746 that I hope this is reverted...)
I think we should wait for this feature to be confirmed, or at at least for parser's response?

Thanks for the discussion at Parser. I thought that it could be introduced to RubyCop AST experimentally, referring to the fact that Ruby Next supports it.
https://github.com/ruby-next/ruby-next

I think we should wait for this feature to be confirmed, or at at least for parser's response?

At least I think we can wait for Parser's response.

https://bugs.ruby-lang.org/issues/16746 that I hope this is reverted...

To be honest, I'm also wondering about adding this syntax to Ruby 😅
Apart from that I added endless? predicate. Thank you.

So parser will output def after all. We could add an endless? predicate that would check the presence of loc.end

Yeah, I will update this PR when Parser <IP_ADDRESS> (or Parser <IP_ADDRESS>) is released. Thank you for your kindness advice!

This PR will be closed due to prefer #129. Thank you @marcandre!

This PR will be closed due to prefer #129. Thank you @marcandre!

My pleasure 😄


ci: tweak ci.yml

After clogging the CI queue with many small commits in #400, I noticed that intermediate builds for pull requests are not cancelled. This fixes it.
@Krastanov If you want this, I can also add it to the other *.yml files.

Thank you! This is very much appreciated, I did not know it exists as a feature. And if you have the bandwidth, I would certainly take you up on the offer to add it to the other workflows.

@Fe-r-oz , thanks to this change, you can now disregard my request to batch multiple small commits in a single large push.


Add approaches route option

This adds a new option, DirectionOptions.approachType, for Indicating how a route considers from which side of the road to approach a waypoint.
/cc @1ec5 @coxchapman

@1ec5 updated to a simple bool.

@1ec5 this is ready for review.

Contrary to https://github.com/mapbox/MapboxDirections.swift/pull/257#issue-180010648, we ended up adding a Boolean-typed RouteOptions.allowsArrivingOnOppositeSide property instead of the enumeration. In the future, if there are new arrival types besides the two currently supported by the Directions API, we can turn this property into a enumeration or add additional properties as appropriate.


Fix FIXME in IsCorrelatedEqualityOpExpr

Fixes the assertion failures from this query from type_sanity test:
SELECT p1.oid, p1.relname
FROM pg_class AS p1
WHERE p1.relnatts != (SELECT count(*) FROM pg_attribute AS p2
WHERE p2.attrelid = p1.oid AND p2.attnum > 0);

Ok, the description of this is not accurate anymore, as I keep adding more patches. I'm going to close this, and reopen a new pull request, and then I'm just going to keep adding patches to my "merge83_equivalence_classes" branch. Feel free to merge that into your branch whenever you get around to it.

Pretty sure I looked like Basil Fawlty there for a while having pushed the one commit in this PR only to come back to close it and find two commits.. =)


issue with remnux upgrade on U20.40

Hi, i have recently tried to upgrade remnux  from V2023.20.1 to v2024.1.3 but it threw error. i went through issues in github but none helped. attached is the logs.
This was a installation from scratch on Ubuntu 20.40.
saltstack.log

solved by rebuilding the image.


Fix spec for out contracts without identifier

Non-void functions can use out without result variable too
Replace HTML tags.
Minor tweaks.

@CyberShadow Any idea why DAutoTest failed on the last commit?

Any idea why DAutoTest failed on the last commit?

code.dlang.org was down.

@wilzbach thanks!


Keep the saved region after receiving config from My-nRF52-Toolbox

Every time a new configuration is received over BLE from My-nRF52-Toolbox the lora_region is overwritten with the option 0. I propose a workaround while this is solved from the My-nRF52-Toolbox side.

Fixed with new WisBlock Toolbox Android application (Soon in the Google Play Store).
Open Source => https://github.com/beegee-tokyo/WisBlock-Toolbox


Generate Json

Hello,
How to generate openapi.json ??
I check this up the commands and i dont see any to generate Annotation based.
Thanks

Hey @mgip,
This package does not generate an openapi.json file in any way.
Its only focus at this time is to allow you to add an openapi.json file and to smooth out the use of the swaggerui library to display that file as a web page.

Package allow set url for openapi json ?


Is there any buffer in server::TlsStream when reading?

I found that second packet of a new connection cannot read by server side, but when client send another packet 5secs later, server side can read normally.

Yes, the rustls ServerConnection does contain an internal buffer, and if we've only received a partial TLS record we'll need to wait for the rest of the contents before we're able to decrypt it.

How to enforce a tls record? In this case, seems we need to let tlsstream generate a complete tls record, not a partial.

Suggest you provide a complete minimal reproduction of your issue.

Closing this for now pending a reproducer.


Added some arrows.

Fixes #153, or rather provides the arrows requested.

These should all be in master now; planning to do a release soon.


ci: improve release workflow

An automated workflow can be triggered from the Actions tab (once this is merged to main) that creates a draft GitHub release. The draft release (notes) can be edited if needed, and then manually converted to an actual Release here, which will trigger the PyPi release (note that a draft release does not trigger PyPi release).
The workflow has the following logic:

Take inputs:

version update level ("patch", "minor", or "major")
release branch

Unfortunately, the default branch cannot be anything else than main, which is almost never the branch we want to release from. Therefore, if main is selected, the workflow fails, because it was likely by accident forgotten to change the default. Releasing from main can still be done manually if needed.

Merge release-branch into main

A conflict will terminate the process before release

Bump the version

install bump-my-version, bump the version on main, push to remote.
NOTE: bump2version is no longer maintained, so its maintained fork bump-my-version is used instead.

Create draft release

the draft can then manually be converted into a published release.

If above is successful, a separate job is started to clean the workspace:

In this way, the "release" will not be listed as failed if below doesn't work (usually due to conflict with dev branch)
changes are merged into dev
the associated PR is closed
if released from a different branch than dev, the hotfix branch is deleted.

This workflow was adapted from here.
fix #170

Very nice improvements to the workflow :D
I added some comments, and requested changes since I'd like to be aware of them (the flow is a bit more complex now, I am like a new developer testing it). Also I wonder, has this workflow being tested? Maybe we can try to do a draft release (that then we cancel) before merging it into dev.

I've made some improvements, mainly to the documentation. I've tested this in the eitprocessing repo, but not yet here. The difficulty is that the action cannot be triggered from the actions tab until it is on the default branch. So either we temporarily change the default branch to test it, or we have to wait for it to be on main to test it.

EDIT: newest tests on eitprocessing aren't working after all 💩 . I will figure it out there and then make changes here. Until then, this PR can stay open.

Okay, I've added a couple of comments still to be addressed. Just ask for my review again when you'll discover what is the fix needed :)

Will do.
I think the best way to test this is to create a fork of the repo, test everything there, and then if it works implement it here as well.

Is this ready to be reviewed again? If not, maybe either remove me from the reviewers or make this PR a draft (otherwise I keep receiving notifications ;))

This action can now be tested on this test fork: https://github.com/EIT-ALIVE/deeprank2_test_release/actions/workflows/release_github.yml. In tested it already and it worked.
Note that in the forked repo, I bugged the release on PyPi action, so that we can still check that it gets triggered, but then fails (I don't think it would have been allowed to release a different repo, but didnt want to find out that somehow it does).
Also, I believe all the issues you @gcroci2 flagged have been addressed, or did I miss anything?
The markdown link check action is failing with an error related to Docker. Is this related to #529 or is it a different problem?

The issue is due to the toml file, where the current version of the package seen from bumpversion does not get updated, and thus the error.
Other remaining things before merging:
* Non-expiring token

* Suggestions

It turns out that the error in the versioning is due to another bump version that occurred in between me creating this PR and now, which still used the old system and didn't update the version listed in bump-my-version-settings. Anyway, I've now moved those settings into a separate toml file to keep the pyproject tidier. I think it would be a good idea to move the ruff settings into a separate toml as well, but that can be done in a separate PR.
See my comments 12 on non-expiring tokens
I've integrated all suggestions to the wording of the dev readme, and ensured that the actions is aborted if dev branch was selected.

I request changes to remember that we need to look at the security thing again. I added a couple of minor suggestions for the instructions. Also let me know if I have to test everything on the fork again (if you say is all good I'll avoid that)

OK, let me know what you decide.
If you want to test again (only minor changes occurred to workflow itself), the please use this new fork instead of the old one. It was quicker to create a new fork rather than update the other one.

[ ] Once we are done testing, we should delete both test forks.

I request changes to remember that we need to look at the security thing again. I added a couple of minor suggestions for the instructions. Also let me know if I have to test everything on the fork again (if you say is all good I'll avoid that)

OK, let me know what you decide. If you want to test again (only minor changes occurred to workflow itself), the please use this new fork instead of the old one. It was quicker to create a new fork rather than update the other one.

[ ]  Once we are done testing, we should delete both test forks.

I tried doing the test, but it gives me: "Releasing from main or dev branch is not permitted, please select a valid release branch." even if I am using a branch called gcroci2-release-test. See here the PR and here the failed action. @DaniBodor

I request changes to remember that we need to look at the security thing again. I added a couple of minor suggestions for the instructions. Also let me know if I have to test everything on the fork again (if you say is all good I'll avoid that)

OK, let me know what you decide. If you want to test again (only minor changes occurred to workflow itself), the please use this new fork instead of the old one. It was quicker to create a new fork rather than update the other one.

[ ]   Once we are done testing, we should delete both test forks.

I tried doing the test, but it gives me: "Releasing from main or dev branch is not permitted, please select a valid release branch." even if I am using a branch called gcroci2-release-test. See here the PR and here the failed action. @DaniBodor

it's fixed

Now the automated release process works great :D the only minor thing left can be to improve the error's triggering if the user selects the main branch from the actions (as I did), because it would fail in this case but it is not clear why (unless you know precisely how the workflow works) @DaniBodor

Now the automated release process works great :D the only minor thing left can be to improve the error's triggering if the user selects the main branch from the actions (as I did), because it would fail in this case but it is not clear why (unless you know precisely how the workflow works) @DaniBodor

@gcroci2
It now displays a message on one of the first steps stating: "Releasing from main or dev branch is not permitted, please select a different release branch."
The workflow in the test repo is now the same as the one here in case you want to test it again.
Apologies for having to go back and forth on this so often

Now the automated release process works great :D the only minor thing left can be to improve the error's triggering if the user selects the main branch from the actions (as I did), because it would fail in this case but it is not clear why (unless you know precisely how the workflow works) @DaniBodor

@gcroci2
It now displays a message on one of the first steps stating: "Releasing from main or dev branch is not permitted, please select a different release branch."
The workflow in the test repo is now the same as the one here in case you want to test it again. Apologies for having to go back and forth on this so often.
On the test repo, I've now tested trying to release from main, dev, or random other branch name, and it gives expected result each time.

Great, merge this :D


Deploying a swarm stack in portainer-ce 2.15.1 creates also a docker (compose) stack

I have deployed version 2.15.1 of portainer-ce today.  All containers run via constraint just on one specific node. The volumes are also just local on this node. Some external, some get created. The deployment creates "magically" also a stack named docker of the type compose. This docker stack includes one of the service containers. Just one, not all. The swarm stack runs fine without any issues. It's just a bit confusing. I am not really sure if it is a bug. What is the reason for the additional compose stack in the ui? I have deployed similar setups on previous versions without the extra limited compose stack.

@jloehel
Can you please provide your stack code for testing?
Thanks!

@jloehel
Can you please provide your stack code for testing?
Thanks!

Thanks for the reply @tamarahenson. Unfortunately that's not possible but I will try to create an minimal stack example which is like the stack next week.

@jloehel
Is this issue related here?  https://github.com/portainer/portainer/issues/8054
Thanks!

@tamarahenson Sorry, I have totally forgotten this issue. Thanks for pinging. Actually it happened only sometimes. I am running currently 2.16.2 and since the last two deployments I haven't seen it again. I don't use com.docker.compose.xxx  labels. I am using the following labels:

org.opencontainers.image.url
org.opencontainers.image.source
org.opencontainers.image.title
org.opencontainers.image.version
org.opencontainers.image.description
org.opencontainers.image.authors
maintainer

... and a few internal labels, which I can't share. But maybe some third-party image used those labels. The stack used also nginx and bitnami/redis but I glanced quickly through those Dockerfiles. It does not look like that.


K8SPXC-172 - Vault keyring

Test name
Status

storage
passed

big-data
passed

init-deploy
passed

recreate
passed

scaling
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

monitoring
passed

upgrade
passed

demand-backup
failed

self-healing-advanced
passed

monitoring-2-0
passed

upgrade-consistency
passed

security-context
passed

operator-self-healing
passed

affinity
passed

one-pod
passed

scheduled-backup
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

Test name
Status

big-data
passed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

scaling
passed

recreate
passed

scaling-proxysql
passed

demand-backup
passed

upgrade
passed

scheduled-backup
failed

upgrade-consistency
passed

init-deploy
passed

security-context
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-361-7630eb08

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

big-data
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

recreate
passed

auto-tuning
passed

demand-backup
passed

proxysql-sidecar-res-limits
passed

scheduled-backup
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed


Add the dual fields to the paraview output

Previously, only the FiniteElementStates (namely the primal solution fields and parameters) were output in Paraview format. This adds the dual fields (e.g. reactions and shape displacement sensitivities) as well for visualization.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (4eeee8e) 89.84% compared to head (64419d0) 89.85%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1041      +/-   ##
===========================================
+ Coverage    89.84%   89.85%   +0.01%
===========================================
  Files          149      149
  Lines        12067    12087      +20
===========================================
+ Hits         10841    10861      +20
  Misses        1226     1226

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@btalamini @white238 @barreracruz , could you take a look at this?


Deployment guide feedback

On page https://aws-ia.github.io/cfn-ps-illumina-dragen/#_feedback
Section heading: Costs and licenses
Documentation issue description:
There is no cost to use this Partner Solution, but you will be billed for any AWS services or resources that this Partner Solution deploys.
But the AMI has a $15 / hr charge for the use of software.

Apologies, I mistook this issue to be the one that you created the PR for.
All Quick Starts are open source and there is no cost to using the open sourced CloudFormation templates and scripts. The resources that you deploy as part of the solution including any Marketplace components and other AWS Services will be billed. In other words, yes, you will have to pay the documented hourly cost for the DRAGEN AMI as documented in the Marketplace listing page. We link to it, but don't include that information inline in the deployment guide to avoid inconsistencies.
Below is the full text in the deployment guide.

There is no cost to use this Partner Solution, but you will be billed for any AWS services or resources that this Partner Solution deploys. For more information, refer to the AWS Partner Solution General Information Guide.
This Quick Start requires a subscription to the Amazon Machine Image (AMI) for DRAGEN Complete Suite, which is available with per-hour pricing from AWS Marketplace.


update number formatting in purchasing

Coverage decreased (-0.002%) to 78.388% when pulling 9eae108a21c6c40577ed0f206196a7b6a4201f2b on achensetyawati:dev into 090da0c8deef7966bb5af63d19bf061f3edce482 on danliris:dev.


"latest" always giving omnisharp version - 1.32.3-beta.9

Setting omnisharp path to "latest" in the C# extension is giving 1.32.3-beta.9 inspite of a PR being merged after this one.

cc @DustinCampbell @rchande @david-driscoll

It just reads whatever version the latest version file specifies.

This has been fixed.


hashids_estimate_encoded_size() performance improvements

I got rid of the conversion of numbers[i] and hashids->alphabet_length to doubles and the conversion of the result from a float to an unsigned long long integer using two tricks I found on stackoverflow:

Fast computing of log2 for 64-bit integers
Fast ceiling of an integer division in C / C++

It should be faster than the equivalent floating point arithmetic.
I also added a test that verifies that hashids_estimate_encoded_size() returns at least the expected hash length.

Strange, the test suite doesn't fail for me locally on OSX.

It also doesn't fail on an Ubuntu 14.04 VM. Can we please merge #13 so that the failures will be printed when the test suite fails?

It turns out I was off by one. I don't know why though.

Well, at least on my Sierra, at -O3, I don't see any performance improvements (tested both CLang and GCC-6)

I'm assuming this will have more effect on large numbers. Let's analyze why this isn't faster.
Floating point arithmetics are certainly slower than normal integer division.
The resulting ASM looks more efficient. I don't know.

Turns out we weren't testing hashids_estimate_encoded_length() at all in our suite.
The results are:
./estimate_encoded_size-old: 0.090
./estimate_encoded_size-new: 0.001

And this PR always provides constant time results.

Merged. I'll do a small refactor and tag a new version.


Some features not available in non-https mode (e.g. albyhub.local)

crypto.subtle which is needed to decrypt the mnemonic locally in order to allow the user to do a key backup
~clipboard copy - I believe we should use a copy library that has a fallback or better support for this situation~

The crypto.subtle issue is still to be fixed. Hopefully by re-thinking the key transport b/w frontend and backend.


Support fabfile.py

I use Fabric in all my python projects. It would be awesome to have an icon for it.
http://www.fabfile.org/

Here's the gliph I created with a free online tool I think it came out decent

After some problem getting the woff2 file I think I managed to get it working.

Yep, looks great!
Just had to remove a few duplicate control points, and change the canvas size so it's square instead of rectangular. I should update CONTRIBUTING.md so users are aware of the need to keep SVGs fitted to a square canvas.


"on:" as keyword becomes "true:"

What steps did you take:
Using ytt data values to generate github actions templates, and the "on:" key becomes "true:".
[template.yml]
#@ load("@ytt:data", "data")
---
name: #@ data.values.action_name
on:
  push:
    branches: #@ data.values.action_branch
    paths: #@ data.values.action_paths
...

What happened:
The "on:" key was replaced by "true:"
[ytt-output]
name: Some name to publish
true: <------------------ expected on: instead of true:
  push:
    branches:
    - master
    paths:
    - .github/workflows/some-docker-image.yml

What did you expect:
Expected the "on:" key to remain
[ytt-output]
name: Some name to publish
on: <------------------ expected on: as the correct output
  push:
    branches:
    - master
    paths:
    - .github/workflows/some-docker-image.yml

Anything else you would like to add:
I figure "on:" might be recognized as a boolean flag somewhere. So I tried "off:" as a keyword to test, and it became "false:" as well. Is there a way to tell ytt to preserve certain keywords as is? Eg.
In the meantime, I'm using sed to replace the piped output before generating the output files.
"on":

to become
on:

Environment:

ytt version v0.31.0 release
Windows 10

Thanks for reporting this. I can confirm being able to reproduce this. As you point out, on and off are interpreted by YAML as boolean values leading to the issue above:
ytt -f /tmp/action/workflow.yml -f /tmp/action/values.yml -s

ytt: Error: Unmarshaling YAML template 'workflow.yml': yaml:
  Strict parsing:
    Found 'on' ambigious (could be !!str or !!bool)

It does look like "on": with quotes around it is still interpreted correctly by actions as a temporary workaround.
Can look a bit further on what the appropriate way to get around this scenario is.

Thanks for reporting this. I can confirm being able to reproduce this. As you point out, on and off are interpreted by YAML as boolean values leading to the issue above:
ytt -f /tmp/action/workflow.yml -f /tmp/action/values.yml -s

ytt: Error: Unmarshaling YAML template 'workflow.yml': yaml:
  Strict parsing:
    Found 'on' ambigious (could be !!str or !!bool)

It does look like "on": with quotes around it is still interpreted correctly by actions as a temporary workaround.
Can look a bit further on what the appropriate way to get around this scenario is.

Going to close this out as it seems to be a duplicate of #146.
The recommended workaround is to have the on key be a string for now ("on":), but we are going to look into prioritizing this as it appears this has come up quite a few times.

Going to close this out as it seems to be a duplicate of #146.
The recommended workaround is to have the on key be a string for now ("on":), but we are going to look into prioritizing this as it appears this has come up quite a few times.


When train in lower bitrates ( < 0.14)?

Hi, thank you for your contributions. Following https://github.com/Justin-Tan/high-fidelity-generative-compression/issues/12, I train the model on my own datasets (very small, contain 10,000 images with size 256*256). I change the values in the target_rate_map dict in default_config.py to [0.05,0.07,0.1]. However, the model shows higher bpp than the pretrained low model (0.14). Specially, the model trained with target rate 0.05 shows poor performance.  And the q_bpp of test is 0.325, while  that of train is 0.078. Could you give me some suggestions.

Fortunately, I found in the next GAN fine-tuning training (low model) that the value of bpp drops and meets expectations.

Fortunately, I found in the next GAN fine-tuning training (low model) that the value of bpp drops and meets expectations.

Hello Shu,
What do you mean by "next GAN fine-tuning"? Have you changed the channel number of output of the encoder?
Thank you!
Sincerely,
Yifei

Fortunately, I found in the next GAN fine-tuning training (low model) that the value of bpp drops and meets expectations.
@JXH-SHU
Hello Shu,
What do you mean by "next GAN fine-tuning"? Have you changed the channel number of output of the encoder?
Thank you!

Sincerely, Yifei

What do you mean by "next GAN fine-tuning"? Have you changed the channel number of output of the encoder?

@JXH-SHU
Hello Shu,
What do you mean by "the next GAN fine-tuning"? Have you changed the channel number of output layer of the encoder?
Thank you!
Sincerely,
Yifei

Fortunately, I found in the next GAN fine-tuning training (low model) that the value of bpp drops and meets expectations.

May I ask how you manage to do that?


Question on comments of discrete interface blocks

Reported by beutlich on 5 Dec 2016 14:22 UTC
Modelica.Blocks.Interfaces.DiscreteSISO / DiscreteMIMO / DiscreteMIMOs apeals abou continuous input/output signals in comments on u, y and the block documentation. Should it be discrete instead?

Migrated-From: https://trac.modelica.org/Modelica/ticket/2123

Modified by beutlich on 5 Dec 2016 14:24 UTC

Comment by hansolsson on 5 Dec 2016 15:59 UTC
Replying to [ticket:2123 beutlich]:

Modelica.Blocks.Interfaces.DiscreteSISO / DiscreteMIMO / DiscreteMIMOs speaks about continuous input/output signals in comments on u, y and the block documentation. Should it be discrete instead?

No, that wouldn't be entirely correct.
In Modelica a Real variable is only discrete-time if assigned in a when-clause.
Thus some Real variables will behave as discrete-time variables (constant between events, discontinuous changes at events) even if they are not formally discrete-time variables.
In this case the inputs to these blocks are normally not assigned in when-clauses (but normally equal to a discrete variable that is), and in one case the output isn't a discrete-time variable, Modelica.Blocks.Discrete.ZeroOrderHold has:
  y = pre(ySample);

I can't remember the exact reason for this, but I recall that the idea is that we should have clear simple rules for when pre(ySample) is valid or not, without having to propagate variability in some unspecified way. Since expressions inside when-clauses are always discrete the downside is in practice very limited. The other implication of discrete-time is that "y>0" will generate a crossing function if "y" is continuous-time and not if "y" is discrete - but as far as I can tell the user cannot detect the presence of crossing function if "y" is "discrete".
Note that the models actually work if the input is an actual continuous-time signal, since the inputs are sampled when used.
Note that e.g. a Gain-block can operate on "discrete" signals and produce "discrete" signals - even if they are formally continuous-time signals.
If we want to change the documentation I would propose that we just remove 'continuous' - or in some cases replace it with 'Real'.
--
The synchronous extension should provide a better solution.