[FEATURE REQUEST] How to Create Stacked Popover with tab

I am just impressed with stacked popover (Not dialog) in Openui5. Is there any way to implement stacked popup in w2ui.
Demo Page: https://openui5.hana.ondemand.com/explored.html#/sample/sap.m.sample.MessagePopover/preview

Once popover is opened, you can update html inside it through $().html(). I do not think there should be any problems with it. I occasiannaly use it to display w2form in it. You can put tabs, or anything else in it. See demos (not directly related) http://w2ui.com/web/demos/#!utils/utils-5


Improve mutex acquisition for promise

Previously, the l2 mutex was not guaranteed, as the future object could become invalid between check and lock. This would cause memory access violation.
Now the l and l2 mutex is acquired from within a global mutex.
The work which happens within the l and l2 locks now happens independently from the locking so that the global mutex is kept locked for minimal time.

Unsure that this will truly fix the crashing. This assumes the global mutex is used by the code responsible for destroying our future (directly or otherwise).
After implementing this, I have not experienced crashing. Generally this crash would come every few hours of runtime.
Additionally, I'm not in love with the unique_lock objects being heap allocations, but it was the "cleanest" approach I could think of without majorly changing this function. It also allowed the removal of the goto/label being used prior.

Needs to be revised and improved. Crash not entirely fixed.


Add haskellProjects.*.{hlintCheck,hlsCheck}.drv

cf. https://github.com/srid/haskell-flake/issues/21#issuecomment-1364154220

This is useless; as we want the whole thing as a string to pass to hci effects.
runCommandInSimulatedShell could perhaps be upstreamed to hci-effects in some form, replacing or complementing its existing nix-shell function.


revert setuptools required upgrade.

Setuptools upgrade in setup.py causing issues for some users.
The fix
Fixes: https://github.com/pypa/pipenv/issues/5075
The checklist

[X] Associated issue
[X] A news fragment in the news/ directory to describe this fix with the extension .bugfix, .feature, .behavior, .doc. .vendor. or .trivial (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

Which version is actually required?
@nomis It is a good question but from my experience many parts of pip and requirementslib pull in the latest setuptools and use it isolation anyway, and there is nothing that can be done about that.

If pipenv doesn't need a newer version (and can be tested with the older version) it shouldn't be specifying it as a dependency.

It always specified this version as a dependency so this is rolling back my prior change, I don't believe we can drop it altogether as it is required.

Won't this still pull setup tools >=60?
Can we Block larger than 60 versions?

Won't this still pull setup tools >=60? Can we Block larger than 60 versions?

This is just reverting it to what it was before, and it seems to work for the folks having the issue, which might just be ubuntu 22.0.4 specific.  I am not convinced that restrict it to less than the latest isn't going to cause different issues for folks that already have a newer version installed at the system level.  Doesn't seem worth it, and internally pipenv is going to pull in the latest setuptools anyway for use in isolation in some spots of requirementslib and pip.

Ok. But pulling this requires a new release (which I'm fine with) but I'm still not sure it's necessary. The issue has a documented solution in the comments. Won't this still be an issue when we upgrade setup tools later?

@oz123 I think it is what @nomis pointed out in the issue comments:

When the setuptools/virtualenv/distutils bug is resolved then pipenv can depend on the newer version of those.

I did take a gamble on updating setuptools in the setup.py when dropping 3.6 support because it seemed like that version is really old, but now it seems this causes issues with whatever the system packaged setuptools or currently installed version is supposed to be so I think we should not restrict it newer yet.  I picked the 60.0.0 version based on which one they dropped 3.6 support in, but alas.
Since pip and requirementslib seem to pull in the latest for some tasks anyway I find it is a complex relationship with setuptools.
Is there a specific issue report in one of those other project @nomis that we could track on if its safe to try forcing the setuptools upgrade at that time?

Ok. Then let's merge this. But we need to keep track of the upstream bug somehow.


Please add CODEOWNERS

See https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

done


(*) is no longer ambiguous

> For any custom operator that starts with *, you'll need to add a white space to the beginning of the definition to avoid a compiler ambiguity. Because of this, it's recommended that you simply surround the definitions of all operators with a single white-space character.
This is no longer true, for example let (*) x y = x + y compiles fine.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8c09996f-24ac-cf39-ef43-d7909cbc2b89
Version Independent ID: 1efdd523-8552-6421-e149-74f76826ef8f
Content: F# code formatting guidelines
Content Source: docs/fsharp/style-guide/formatting.md
Product: dotnet-fsharp
GitHub Login: @cartermp
Microsoft Alias: phcart

I think this was just poorly-worded. Re-defining * is unambiguous, but using it in conjunction with other characters becomes a problem.


improve vim plugin updater: per-plugin update (+ add it as a flake.nix application ?)

Issue description
I would like to be able to call the vim updater to update specific plugins and only these plugins (same for luarocks updater).
For instance in https://github.com/NixOS/nixpkgs/pull/218578, I would like to just update these plugins without regenerating the full set.
Which is anyway impossible at the moment because github flagged some github accounts as suspicious and made those repositories unavailable:
https://github.com/orgs/community/discussions/48173#discussioncomment-5117119
1183 plugins were checked, 3 plugin(s) could not be downloaded:

PluginDesc(repo=Repo(Spacegray.vim, https://github.com/ackyshake/Spacegray.vim/), branch='', alias=''): HTTP Error 404: Not Found
Traceback (most recent call last):
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 602, in prefetch
    plugin, redirect = prefetch_plugin(pluginDesc, cache)
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 477, in prefetch_plugin
    commit, date = repo.latest_commit()
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 71, in f_retry
    return f(*args, **kwargs)
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 187, in latest_commit
    with urllib.request.urlopen(commit_req, timeout=10) as req:
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 216, in urlopen
    return opener.open(url, data, timeout)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 525, in open
    response = meth(req, response)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 634, in http_response
    response = self.parent.error(
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 563, in error
    return self._call_chain(*args)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 496, in _call_chain
    result = func(*args)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 643, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found
PluginDesc(repo=Repo(VimCompletesMe, https://github.com/ackyshake/VimCompletesMe/), branch='', alias=''): HTTP Error 404: Not Found
Traceback (most recent call last):
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 602, in prefetch
    plugin, redirect = prefetch_plugin(pluginDesc, cache)
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 477, in prefetch_plugin
    commit, date = repo.latest_commit()
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 71, in f_retry
    return f(*args, **kwargs)
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 187, in latest_commit
    with urllib.request.urlopen(commit_req, timeout=10) as req:
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 216, in urlopen
    return opener.open(url, data, timeout)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 525, in open
    response = meth(req, response)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 634, in http_response
    response = self.parent.error(
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 563, in error
    return self._call_chain(*args)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 496, in _call_chain
    result = func(*args)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 643, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found
PluginDesc(repo=Repo(Vundle.vim, https://github.com/VundleVim/Vundle.vim/), branch='', alias=''): HTTP Error 404: Not Found
Traceback (most recent call last):
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 602, in prefetch
    plugin, redirect = prefetch_plugin(pluginDesc, cache)
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 477, in prefetch_plugin
    commit, date = repo.latest_commit()
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 71, in f_retry
    return f(*args, **kwargs)
  File "/home/teto/nixpkgs3/maintainers/scripts/pluginupdate.py", line 187, in latest_commit
    with urllib.request.urlopen(commit_req, timeout=10) as req:
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 216, in urlopen
    return opener.open(url, data, timeout)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 525, in open
    response = meth(req, response)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 634, in http_response
    response = self.parent.error(
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 563, in error
    return self._call_chain(*args)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 496, in _call_chain
    result = func(*args)
  File "/nix/store/iw1vmh509hcbby8dbpsaanbri4zsq7dj-python3-3.10.10/lib/python3.10/urllib/request.py", line 643, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found

On a sidenote, I wondered if we could add the script to the root's flake.nix's application, so that one can run nix run .#update-vim-plugins. This way we can enjoy nix autocompletion, it helps with discovery and one doesn't need to fd update.py to find the updater script
Steps to reproduce
$ pkgs/applications/editors/vim/plugins/update.py --proc 5
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

I am starting a PR to add subcommands (update.py add / update.py update), this will help making the CLI evolve. For instance I would like to run update.py update plenary.nvim  to update ONLY 'plenary.nvim'.
update.py add plugin1.vim should just add the plugin without updating everything.


Josephus Problem Algorithm

The Josephus Problem is a mathematical problem that involves a group of people standing in a circle, where every nth person is eliminated until only one person remains. The problem is to determine the position of the last remaining person.
Here's an algorithm to solve the Josephus Problem:
Start with a list or an array representing the circle of people, where each person is assigned a unique identifier or position.
Choose a starting position, typically denoted as "k" or "s". This is the position of the first person to be eliminated.
Determine the value of "n", representing the step size or count. This is the number of positions to skip before eliminating the next person.
Repeat the following steps until only one person remains:
a. Start at the current position "k".
b. Count "n" positions in a clockwise direction, skipping any eliminated positions.
c. Eliminate the person at the current position.
d. Update the current position "k" to the next available position after the elimination.
The person remaining after all eliminations is the solution to the Josephus Problem.

@Kumar-laxmi Kindly assign this issue to me

Assigned!
@Devchawla2608 : C, C++, Python and Java


Prevents Mod Engine 2 from launching when used with the latest version of the game

Launching Elden Ring through Mod Engine 2 with this DLL in the config file prevents the game from launching. I have not tested using Mod Loader instead of Mod Engine 2, but this started happening with the latest Elden Ring update (1.12) and the DLC (Shadow of the Erdtree) release.

I assume you did update your version of the altsaves mod? Try this one if not: https://github.com/vswarte/eldenring_alt_saves/releases/tag/v1.3.2

I assume you did update your version of the altsaves mod? Try this one if not: https://github.com/vswarte/eldenring_alt_saves/releases/tag/v1.3.2

My bad. It was the Nexus version of the mod, which hasn't been updated. I did not notice the latest update here.


I can't get my lua Bullet notes to not change colors in 0.7.3.

Describe your problem here.
I'm working on a modpack that remixes songs, similar to B-Side or Neo, and wanted to add some bullet notes to blammed, just for a bit of extra challenge, but my keep changing to whatever color I have for the border is (RGB value B) for my notes!

I've tried to do alters with the code (using ChatGPT for help because I don't know how to program as of now) but nothing I do works. How do I fix this?
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
I did some small edits to the code just to change the name of the application and a few other miniscule changes like different fonts in different menus.

If this is coded in LUA, could you send the Script?

In your note, you need to put this code:
for i = 0, getProperty('unspawnNotes.length')-1 do if getPropertyFromGroup('unspawnNotes', i, 'noteType') == 'YourNoteName' then setPropertyFromGroup('unspawnNotes', i, 'rgbShader.enabled', false);
Hope this works for you! (If you already have the first 2 lines for the texture, just add the third line after the texture line).

If this is coded in LUA, could you send the Script?

https://drive.google.com/file/d/1BPp5685K8KH9rwMohnhWU5dgNWnqxslH/view?usp=sharing

I figured the script out.


[BUG] Last cell doesn't get returned in the array if it's empty

🐛 Bug Report

When trying to read an excel file, the array containing each row columns values doesn't return the last cell if it's empty (the same problem if we have more consecutive empty cells at the end of the row, they don't get returned)
I tried this option: { includeEmpty: true } but it works just if the cells are in the middle of the row not at the end.

the arrays returned also contain always an empty field (null), in the beginning, even though there is not an empty cell at the beginning of each row in the excel file

Lib version: 4.1.1
Steps To Reproduce
                        const wb = new ExcelJS.Workbook();
			const reader = new FileReader()
			reader.readAsArrayBuffer(this.file)
			reader.onload = () => {
				const buffer = reader.result;
				wb.xlsx.load(buffer).then(workbook => {
					workbook.eachSheet((sheet, id) => {
						sheet.eachRow({ includeEmpty: true }, (row, rowIndex) => {
							console.log(row.values, row.values.length, rowIndex)
							if(rowIndex !== 1) this.fileArrayData.push(row.values.splice(1))
						})
					})
				}).catch(error => {
				})
			}

The expected behaviour:
Get an array of each row without the empty field (null) at the beginning of each one of them
Get the last consecutive cells even if they are empty.
Possible solution (optional, but very helpful):

I d faced the same bug. I also noticed that in such case sheet.columnCount returns right value. Also, I noticed that If I call the next code before using eachRow starts work correctly.
    sheet.columns.forEach(c => {
        c.eachCell?.({ includeEmpty: true }, cell => {
          //OD NOTHING
        })
    })

I encountered the same bug. How did you fix it? I don't quite understant what you did.
sheet.columns returns a number suposedly

any resolution to this BUG WHICH TOOK ME AGES TO FIND?

here is a temporary workaround, hope you can make sense of it:
async convertXlsToCsv(xlsBuffer) {
        const workbook = new ExcelJS.Workbook();
        await workbook.xlsx.load(xlsBuffer);

        const csvBuffer = await workbook.csv.writeBuffer({
            formatterOptions: {
                includeEndRowDelimiter: true,
                transform: (row) => {
                    // this is a scary workaround, i know, but it works
                    row.length = row.length + 1;
                    return row.fill(row.length, row.length + 1);
                },
            },
        });

        return csvBuffer;
    }

The includeEmpty is the way to go, I've did this:
const rowData: (string | number | boolean | Date | ExcelJS.CellErrorValue | ExcelJS.CellRichTextValue | ExcelJS.CellHyperlinkValue | ExcelJS.CellFormulaValue | ExcelJS.CellSharedFormulaValue | null | undefined)[] = [];

                row.eachCell({ includeEmpty: true }, (cell) => {
                        const cellValue = cell.value === null || cell.value === undefined ? null : cell.value;
                        rowData.push(cellValue);
                });

                data.push(rowData);

The includeEmpty is the way to go also, can we close this?, I've did this:
const rowData: (string | number | boolean | Date | ExcelJS.CellErrorValue | ExcelJS.CellRichTextValue | ExcelJS.CellHyperlinkValue | ExcelJS.CellFormulaValue | ExcelJS.CellSharedFormulaValue | null | undefined)[] = [];

                row.eachCell({ includeEmpty: true }, (cell) => {
                        const cellValue = cell.value === null || cell.value === undefined ? null : cell.value;
                        rowData.push(cellValue);
                });

                data.push(rowData);

This doesn't work, that why we are talking about it here.

I faced the same bug. I also noticed that in such case sheet.columnCount returns right value. Also, I noticed that eachRow starts work correctly, If I call the next code before
    sheet.columns.forEach(c => {
        c.eachCell?.({ includeEmpty: true }, cell => {
          //OD NOTHING
        })
    })
   sheet.getRow(2).eachCell({includeEmpty: true}, (cell, colNumber) => {
    //NOW EVERY CELL IS PRESENT
  })

For anyone still facing this issue, this workaround worked for me.


feat: Improve etcdop framework

Jira: https://keboola.atlassian.net/browse/PSGO-596
All tests will pass in the final PR.
Large set of fixes and E2e tests is divided into smaller PRs to do a review.

Changes:

Various improvements and fixes in etcdop framework, see comments.

Commend per commits.

At first, please read AtomicOp docs:
https://github.com/keboola/keboola-as-code/blob/a8001e970c4b56222dfdc7e907b1d2fce18fde9a/internal/pkg/service/common/etcdop/op/atomic.go#L14-L34

I'll have to take a closer look at etcd. 👍


Do you have a schedule

Very interesting project. What to try and help, do you have a schedule?

I'm almost done. need some refinement and documentation. The basic feature should be ready by Monday.

you are my hero


feat: switch to updated version of tinyexec

Description
Originally submitted in https://github.com/antfu/install-pkg/pull/12 and then reverted in e50016c9e4002cbb2d497dbdefe11fa0d53df6b0. This reverts the revert to try again with a fixed version of tinyexec.
https://npmgraph.js.org/?q=@jsdevtools/ez-spawn - 9 dependencies
https://npmgraph.js.org/?q=tinyexec - 0 dependencies
@jsdevtools/ez-spawn also has not been updated in 4 years
Linked Issues
See https://github.com/antfu/install-pkg/pull/11#issuecomment-2273764981
Additional context
vitest would like to switch to tinyexec, but they use this library so are waiting for it to be switched first so that they can keep dependencies in sync

@benmccann Nice! I will switch taze's ezspawn w/ tinyexec as well.

Heads up that I ran into an issue from this today, so you might want to hold off for just a little bit. See https://github.com/tinylibs/tinyexec/issues/32


Discussion: improve hints

Right now dry-validation create hints in some cases, honestly I'm not sure when it happen.
This kind of behavior goes against the general explicit behavior or dry-v.
Sample:
TheSchema = Dry::Validation.Schema do
  required(:name).value(:str?, :filled?, :gt?: 2, :cant_be_a_john?)
end

TheSchema.(name: "")

# messages={:name=>["name is missing", "name has to be gt 2", "sorry we don't like Johns"]}

Some apps would like this behavior, but some wont, probably some need this behavior only for a specific key or schema.
We could have a config.hints option that could be used for the entire schema. The options could be true | false, or maybe a "level" of hinting like: [:all, :type_check, :custom_predicates, :builtin_predicates], not sure if this would be possible or even viable.
Another way to set the hints could be per key. Something like: required(:name).value(:str?, :filled?, :gt?: 2, :cant_be_a_john?).hints(:cant_be_a_john?).

This should be done prior 1.0

I was always under the impression that hints would be stored under a different key than actual error messages, would it not be simpler to just do

@AMHOL yeah it crossed my mind too but I thought it's gonna be way too different from "typical validation libs" and people may get confused, now I'm on the fence heh

@solnic it's already way too different from typical validation libs, I see that as a positive :wink:

I like @AMHOL suggestion, wouldn't that be easier also? What about: messages(:hints)?

Yeah this is the downside so we should think this through. It would not
simplify the implementation of the hint compiler BUT it would not require
additional features in the DSL. So pros and cons...
On Wed, 13 Apr 2016 at 19:01, Ralf Schmitz Bongiolo <
<EMAIL_ADDRESS>wrote:

I like @AMHOL https://github.com/AMHOL suggestion, wouldn't that be
easier also? What about: messages(:hints)?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/dry-rb/dry-validation/issues/104#issuecomment-209546389


bug fixed

self.protocol.callPing(bucket.head())
bug fixed: Use synchronous call to an asynchronous function
asyncio.ensure_future(self.protocol.callPing(bucket.head()))
I just started to use github, so don't be puzzled to see so many commits. : )
And would you mind I ask a question? I'm a bit confused in the using asyncio. When I create a loop in class server, should I create another loop in the class ForgetfulStorage if I want to do something asynchronous in the storage? So where exactly the loop in? In the instance? It seems to be everywhere in my code. : )

Good catch!  I had one comment just wondering why a line was moved - other than that thanks for catching this!
There should only be one loop - and asyncio.get_event_loop() will always return that one instance.


Missing FgAirplayChannel

Source files FgAirplayChannel.cpp and FgAirplayChannel.h is missing in the project

Appended the missing files.


document Executable is now in std lib as of go1.8

Hi,
See https://beta.golang.org/pkg/os/#Executable

Thanks, I'm aware. It would be good to add documentation to this project to that effect.

Document that the Executable call is now in "os" in both godoc and README.

@kardianos Would you encourage using os.Executable over osext.Executable, or are there any reasons to stick with osext (aside from support for Go 1.7 and older)?

@shurcooL I'd switch to os.Executable.
I've pushed this update so it is ready for go1.8.


TypeError: Cannot read property '0' of undefined

Hi, I just switched to your branch because OwenCalvin's slash branch is currently broken. Thanks for making your fork available via npm.
When registering a command with option I get a TypeError (see title), it's caused by this code:
@Discord()
export abstract class Credits {
  @Slash("credits")
  credits(
    @SlashOption("x", { description: "x value" })
    x: number,
    interaction: CommandInteraction
  ): void {
    interaction.reply("credits response");
  }
}

The full stacktrace is:
TypeError: Cannot read property '0' of undefined
    at /home/jetse/projects/BetaClimbers/DiscordBot/node_modules/discordx/src/decorators/decorators/SlashOption.ts:26:72
    at /home/jetse/projects/BetaClimbers/DiscordBot/node_modules/tslib/tslib.js:104:41
    at DecorateProperty (/home/jetse/projects/BetaClimbers/DiscordBot/node_modules/reflect-metadata/Reflect.js:553:33)
    at Reflect.decorate (/home/jetse/projects/BetaClimbers/DiscordBot/node_modules/reflect-metadata/Reflect.js:123:24)
    at Object.__decorate (/home/jetse/projects/BetaClimbers/DiscordBot/node_modules/tslib/tslib.js:98:96)
    at /home/jetse/projects/BetaClimbers/DiscordBot/src/commands/Credits.ts:7:3
    at Object.<anonymous> (/home/jetse/projects/BetaClimbers/DiscordBot/src/commands/Credits.ts:5:1)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Module._compile (/home/jetse/projects/BetaClimbers/DiscordBot/node_modules/source-map-support/source-map-support.js:547:25)
    at Module.m._compile (/tmp/ts-node-dev-hook-2853484122283596.js:69:33)

After looking at the source and some experimentation I found that manually specifying the type fixes the error. That works, but is less than ideal.
@Discord()
export abstract class Credits {
  @Slash("credits")
  credits(
    @SlashOption("x", { description: "x value", type: "INTEGER" })
    x: number,
    interaction: CommandInteraction
  ): void {
    interaction.reply("credits response");
  }
}

With debugging I could verify that Reflect.getMetadata("design:paramtypes", target, key) returns undefined. I have no idea beyond that what the problem is (nor did I really investigate). If you need more information, just let me know.

Nevermind, I found the problem: I didn't have emitDecoratorMetadata enabled in tsconfig.json :facepalm:. Should've read the docs more carefully.


Cannot execute app release with Proguard 7.4.2

Describe the bug
When trying to execute runReleaseDistributable, app fails with this error:
Exception in thread "main" java.lang.VerifyError: Bad return type
Exception Details:
  Location:
    androidx/compose/runtime/SnapshotStateKt__DerivedStateKt.derivedStateOf$102ee4b4(Landroidx/compose/runtime/SnapshotMutationPolicy;Lkotlin/jvm/functions/Function0;)Landroidx/compose/runtime/DerivedSnapshotState; @24: areturn
  Reason:
    Type 'androidx/compose/runtime/State' (current frame, stack[0]) is not assignable to 'androidx/compose/runtime/DerivedSnapshotState' (from method signature)
  Current Frame:
    bci: @24
    flags: { }
    locals: { 'androidx/compose/runtime/SnapshotMutationPolicy', 'kotlin/jvm/functions/Function0' }
    stack: { 'androidx/compose/runtime/State' }
  Bytecode:
    0000000: 2a12 07b8 0017 2b12 06b8 0017 bb00 0859
    0000010: 2b2a b700 12c0 000c b0

	at androidx.compose.runtime.ComposerImpl.doCompose(Composer.kt:50241)
	at androidx.compose.runtime.ComposerImpl.composeContent$runtime(Composer.kt:3236)
	at androidx.compose.runtime.CompositionImpl.composeContent(Composition.kt:725)
	at androidx.compose.runtime.Recomposer.composeInitial$runtime(Recomposer.kt:1071)
	at androidx.compose.runtime.CompositionImpl.composeInitial(Composition.kt:633)
	at androidx.compose.runtime.CompositionImpl.setContent(Composition.kt:619)
	at androidx.compose.ui.window.Application_desktopKt$awaitApplication$2$1$2.invokeSuspend(Application.desktop.kt:219)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
	at java.desktop/java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source)
	at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
	at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
	at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)

Affected platforms
Select one of the platforms below:

Desktop

Versions

Kotlin version*: 1.9.20 and 1.9.22
Compose Multiplatform version*: 1.5.10 and 1.5.12 and 1.6.0
OS version(s)* (required for Desktop and iOS issues): Windows 11
OS architecture (x86 or arm64): x86
JDK (for desktop issues): Oracle OpenJDK 21

Expected behavior
The app should run when executing runReleaseDistributable.

For a workaround, I added this line to my rules.pro file:
-dontoptimize

Do you use Material 3 or 2? Did you try with the default libraries included with the template without changing or including third-party libraries? Because Material 3 is not supported yet.

Another workaround without disabling Proguard optimizations:
-keep class androidx.compose.runtime.** { *; }
-keep class kotlinx.coroutines.** { *; }

This will exclude Kotlinx coroutines from minimization, the bundle size will be 29.4 MB for the example desktop app on macOS Apple silicon JAR file, previously 28.3 MB with the runtime error
Tested with Compose 1.6.10, Proguard 7.5.0, and Kotlin 2.0.0 with a project created by kmp.jetbrains.com

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.

EchoEllet I'm using Material 2.
Thanks for the tip.

EchoEllet I'm using Material 2. Thanks for the tip.

I was able to use it with Proguard 7.5.0, Kotlin 2.0.0 and Material 3 with this workarorund


[Bug] Move: duplicate definition for BCS

🐛 Bug

To reproduce
Note: this was captured on 2/14/2021

follow steps at https://developers.diem.com/docs/move/move-tutorial-creating-coins/
at step '$ move publish src/modules'
==> as seen in attached screenshot, system fails out with 'duplicate definition for BCS'

Code snippet to reproduce
# Your code goes here
# Please make sure it does not require any external dependencies

Stack trace/error message
duplicate definition for BCS
// Paste the output here

## Expected Behavior

<!-- A clear and concise description of what you expected to happen. -->

## System information

**Please complete the following information:**
- <!-- Diem Version -->
- <!-- Rust Version -->
- <!-- Computer OS -->
macos 11.2.1
<img width="1280" alt="moveError" src="https://user-images.githubusercontent.com/7838889/111819755-f5cc9300-889d-11eb-8f14-d51fe4a673cd.png">

## Additional context

Add any other context about the problem here.

When you run move publish src/modules, the Move CLI will compile all the Move source files in the src/modules directory, and it appears that you somehow got copies of the Move standard library interface files there. The compiler also includes the Move standard library by default, so you're getting 2 copies of all those files (BCS.move and Compare.move show up in the screenshot). My guess is that you previously tried running the command from inside the src/modules directory and the tool wrote out the interface files in the build/mv_interfaces directory. If you look closely at the steps for the tutorial, you'll see that it says to do cd toycoin (i.e., the parent directory of src/modules) and the assumption is that you'll run the commands from there. If you remove the src/modules/build directory, and then run the command from the toycoin directory, it should work.


Release 4.9.0

Firebase 4.9.0 has published.  Update the versions in master.

Merging on travis green


Don't catch BaseException

I agree with this. Bare except: clauses are invariably wrong. I'd like to leave this open for a more-complete correction (since this is effectively a no-op; let's hope to at least take one or more steps to fix).


Add Classifier documentation and example

Description of Classifier eBPF programs and example of egress filtering.
Signed-off-by: Michal Rostecki<EMAIL_ADDRESS>

Thanks @vadorovsky LGTM


anchor fails windows

Hello,
I started a brand new project on Windows x64.
When I do cargo metadata from my project folder, it works correctly and I get an expected output.
When I do from the same folder anchor test or anchor build, it is not working and I get the following output:
Failed to obtain package metadata: 'cargo metadata' exited with an error: error: failed to load manifest for workspace member '\\?\C:\Users\thugu\Documents\OneDrive\OneDrive_Doc\Crypto-project\solequapp\programs\*'

Caused by:
  failed to read '\\?\C:\Users\thugu\Documents\OneDrive\OneDrive_Doc\Crypto-project\solequapp\programs\*\Cargo.toml'

Caused by:
  The filename, directory name, or volume label syntax is incorrect. (os error 123)

I dont understand why the path generated looks like this with anchor while it is correct when doing the cargo metadata directly.
Any help welcome.
Thanks

I also face some issue in installing anchor!!!!!! in windows 11

Use the WSL2 Ubuntu, works like charm for me

As a workaround without using WSL, what you can do here is execute the command which anchor test is running (see your Cargo.toml). In this case that would be something like yarn run ts-mocha -p ./tsconfig.json -t 1000000 tests/**/*.ts for the repo I have set up.
It seems like there may be an issue to the path building logic in anchor vs. something with your local setup. I don't know the code well, so not sure where to fix at the moment, but I think it might be in https://github.com/project-serum/anchor/blob/a604f8595c875a23b8e13c8569577d6a6b1c79bd/cli/src/config.rs .

In desperate need of an actual solution. I can't find anything on it.

Hey @JacobWarner this development cycle works great for me.
# Make sure you’re on the localnet.
solana config set --url localhost
# And check your Anchor.toml file.

# Code…

# Run the tests.
anchor test

# Build, deploy and start a local ledger.
anchor localnet
# Or
solana-test-validator
anchor build
anchor deploy

# Copy the new IDL to the frontend.
anchor run copy-idl

# Serve your frontend application locally.
npm run serve

# Switch to the devnet cluster to deploy there.
solana config set --url devnet
# And update your Anchor.toml file.

# Airdrop yourself some money if necessary.
solana airdrop 5

# Build and deploy to devnet.
anchor build
anchor deploy

# Push your code to the main branch to auto-deploy on Netlify.
git push

For Ref use this link : https://lorisleiva.com/create-a-solana-dapp-from-scratch/getting-started-with-solana-and-anchor
I have used it on Windows WSL2 and Linux and MacOS 12 (M1 Pro) all works perfectly fine. Reach out if you need help and can provide with a github git if you need.

Hello
Thank you for your replies.
I use Windows WSL2 and with your tip, got it working. Cheers

using wsl is a work around not a fix, not sure why the issue was closed

I face same issue on windows 10. Isn't there any other way except for using WSL?

I face same issue on windows 10. Isn't there any other way except for using WSL?

@amTechie I actually looked into this for a bit. Turns out the issue is with solana cli, which anchor calls for quite a few things. Right now, outside of fixing it in solana cli, you need to resort to WSL.
All in all it isn't that big of a change. Just make sure you run your local validator from the WSL Home area, not the default Windows home. You can set up a profile w/ Windows Terminal that just automates this.

Setting your HOME env variable on windows fixes this issue.
I had this issue on windows and set HOME env variable to C:/Users/MyUserName
"anchor build" runs cargo build-bpf which checks for HOME env variable ( see link below ) . On bash shells this is set automatically, but its not set on windows cmd prompt terminal.
https://github.com/solana-labs/solana/blob/d5dec989b93fc94c9416a60193e52e8b68bd7133/sdk/cargo-build-bpf/src/main.rs#L474

@metta0714 I did this. Still same error

I noticed this error happened when I added dependencies in the cargo toml at the root of my project.
Add all your dependencies in the programs/<>/cargo.toml folder


migration examples to ce3

Partially fix https://github.com/http4s/http4s/issues/4093
Ember examples are missing as ember is not migrated to ce3 yet (https://github.com/http4s/http4s/issues/4085 https://github.com/http4s/http4s/issues/4086)
I could not start the blaze examples:
[info] running (fork) com.example.http4s.blaze.ClientExample
[info] -Xbootclasspath/p is no longer a supported option.
[error] Error: Could not create the Java Virtual Machine.
[error] Error: A fatal exception has occurred. Program will exit.

I don't know if this is a known issue.

Still an overseen warning to fix:
[error] /home/runner/work/http4s/http4s/examples/blaze/src/main/scala/com/example/http4s/blaze/BlazeWebSocketExample.scala:72:9: object Queue in package concurrent is deprecated (since 3.0.0): Use cats.effect.std.Queue instead
[error]         Queue
[error]         ^
[error] one error found

Still an overseen warning to fix:
[error] /home/runner/work/http4s/http4s/examples/blaze/src/main/scala/com/example/http4s/blaze/BlazeWebSocketExample.scala:72:9: object Queue in package concurrent is deprecated (since 3.0.0): Use cats.effect.std.Queue instead
[error]         Queue
[error]         ^
[error] one error found

That parameter is for ALPN support, which isn't necessary after Java 8 and probably should be filtered accordingly.  But we test on newer JDK, so I'm not sure why you'd be hitting that.  Which JDK did you hit that error on?
If you disable AlpnBootPlugin, that should go away... but so will HTTP/2 support.

That parameter is for ALPN support, which isn't necessary after Java 8 and probably should be filtered accordingly.  But we test on newer JDK, so I'm not sure why you'd be hitting that.  Which JDK did you hit that error on?
If you disable AlpnBootPlugin, that should go away... but so will HTTP/2 support.

That parameter is for ALPN support, which isn't necessary after Java 8 and probably should be filtered accordingly. But we test on newer JDK, so I'm not sure why you'd be hitting that. Which JDK did you hit that error on?

$ javac -version
javac 15.0.1

$ java -version
openjdk version "15.0.1" 2020-10-20
OpenJDK Runtime Environment AdoptOpenJDK (build 15.0.1+9)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 15.0.1+9, mixed mode, sharing)

If you disable AlpnBootPlugin, that should go away... but so will HTTP/2 support.

Thanks, I've tried that, and the examples are working:
 lazy val examplesBlaze = exampleProject("examples-blaze")
-  .enablePlugins(AlpnBootPlugin)
   .settings(Revolver.settings)

That parameter is for ALPN support, which isn't necessary after Java 8 and probably should be filtered accordingly. But we test on newer JDK, so I'm not sure why you'd be hitting that. Which JDK did you hit that error on?

$ javac -version
javac 15.0.1

$ java -version
openjdk version "15.0.1" 2020-10-20
OpenJDK Runtime Environment AdoptOpenJDK (build 15.0.1+9)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 15.0.1+9, mixed mode, sharing)

If you disable AlpnBootPlugin, that should go away... but so will HTTP/2 support.

Thanks, I've tried that, and the examples are working:
 lazy val examplesBlaze = exampleProject("examples-blaze")
-  .enablePlugins(AlpnBootPlugin)
   .settings(Revolver.settings)

Oh, and it's in run / javaOptions, which is why CI doesn't catch it.  We can fix it in the org plugin, and it'll work here, for upstream blaze, and for anything else that needs it for HTTP/2 support.

Oh, and it's in run / javaOptions, which is why CI doesn't catch it.  We can fix it in the org plugin, and it'll work here, for upstream blaze, and for anything else that needs it for HTTP/2 support.


404 Error when accessing admin panel page on http://localhost:8000/tgadmin/

Hello!
I tried both running bot locally and using docker compose and adding a new django user with python manage.py createsuperuser.
In both cases I receive 404 error when trying to access the http://localhost:8000/tgadmin/ page from README guide. What do I do wrong?

Reran docker compose, tried another user credential and all worked fine


Add mode argument to webpack

As they explain in here, with webpack 4 they started soft-requiring this argument.

Thanks!


add landing page

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

File
Status
Preview URL
Details

Odata-docs/index.yml
:white_check_mark:Succeeded
View

Odata-docs/overview.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 35fd05a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/index.yml
:white_check_mark:Succeeded
View

Odata-docs/overview.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 7dc4e97:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/index.yml
:white_check_mark:Succeeded
View

Odata-docs/overview.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/index.yml
:white_check_mark:Succeeded
View

Odata-docs/overview.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 790a573:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/index.yml
:white_check_mark:Succeeded
View

Odata-docs/overview.md
:white_check_mark:Succeeded
View

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


Bug: Can't Change Item Image

When editing an item, selecting a new image file does not replace the existing image.

The thumbnail doesn't change after selecting, but does change when pressing save save. Issue is the file doesn't upload until the form is submitted. Might be able to blank the old image on upload of an image

I've just tried again, and it isn't uploading/changing image when pressing save.

Ok, so it looks like the thumbnail in the listing has changed, but not the main/larger image on the product listing page/popup.

See AKG D40 Tom Microphone on Trevs page for demo.

Ok, so the D40 looks fine now. @Jon-Salmon did you do something in the database, or did it sort itself out? But I've just tried to change the scaff bar image, and it won't change.


pulumi: 0.17.27 -> 1.1.0

Motivation for this change
Bringing in the latest stable version of the tool
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @peterromfeldhk

@GrahamcOfBorg build pulumi

@mmahut,  do you know if I need to do anything for the checks with  "No attempt" status?

@GrahamcOfBorg build pulumi-bin


Reflect derived traits on all components and resources

What problem does this solve or what need does it fill?
Some components and resources reflect their derived traits (e.g. Name), but most only derive some of them (e.g. Transform).
To me it is unexpected that I have to manually add some fundamental traits (like Default, Debug, Serialize and Deserialize) to the reflection system retroactively. This way the user can rely on the consistency of which traits are reflected.
A practical example is a plugin I'm working on. It has to serialize entities using the reflection system.
It serializes all components that have ReflectSerialize. But by default that leads to partial serializations.
What solution would you like?
I propose to add reflection to the following traits on components and resources that implement them:

Default
Debug
Hash
PartialEq
Serialize
Deserialize
Component (I did not find an example where this one is actually missing. It's in this list for completeness sake)

All of these are already reflected on some component.
What alternative(s) have you considered?
It is of course possible to go through the bevy code and manually register all bevy types:
app.register_type_data::<X, ReflectSerialize>().register_type_data::<X, ReflectDeserialize>();

The problems with this approach are:

Consistency. Some components and resources don't need to be added like this.
Maintenance burden on generic code when new components are introduced. Since reflection only shows up at runtime this can lead to bugs easily.

Additional context
Additional notes:
It is necessary to benchmark compile times. The macro increases compile times. If the compile times become unacceptable the set of traits added to reflection needs to be reviewed. Taking traits out of the reflection system in a consistent manner would be  breaking changes as some types already make use of these.
Feature gates need to be respected (particularly bevy_reflect and serialize). At this point I still need to review which feature gates exist for which subcrates.

This should be done, but is easy to forget. When tackling this, please handle it one crate or so at a time: it's helpful to avoid merge conflicts and review burden.

I'm working on this but can only get started on Sunday, so no pull request just yet.
Should I open one pull request per crate?
I'm also wondering if a lint could be written to remind people to do this on future components and resources.
I'll investigate that one when I'm done with this issue.

FYI, there was talk of deprecating reflect(Debug), so by adding this, you may be increasing future workload. Can we skip that one? Ping @MrGVSV

FYI, there was talk of deprecating reflect(Debug), so by adding this, you may be increasing future workload. Can we skip that one? Ping @MrGVSV

I'm on the fence about deprecating it. I agree that generally speaking, the reflection-based Debug impl should work for most cases. However, there are many cases where a custom Debug impl might be desired. And the PR to deprecate it (#11625) uses autoref specialization magic to automatically implement it.
I'd like to see benchmarks and/or a breakdown of performance, maintainability, and support implications before committing to that idea. Or at the very least, I'd like to know that Bevy is comfortable with utilizing these quasi-specialization hacks.
Until then, I think it's perfectly fine—and probably desirable—to add reflect(Debug) to types.

I went through all subcrates and fixed everything I could find. I consider this done.

@blazepaws much appreciated, thanks!


Clarification of hourly billing

Can you please clarify that the billing is based on wall clock hours and not duration hours?  In other words, if I scale a collection up to 1000 RUs at 9:59 AM, and then scale it back down to 400 RUs at 10:01 AM, my collection is scaled up for a duration of 2 minutes.  According to the documentation:
Billing rate when container or a set of containers are active for less than an hour
You're billed the flat rate for each hour the container or database exists, no matter the usage or if the container or database is active for less than an hour. For example, if you create a container or database and delete it 5 minutes later, your bill will include one hour.

So, in my scenario, do I pay for two hours at the rate of 1000 RUs (two wall clock hours) or do I pay 1 hour (duration hours)?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 09911b22-f73f-d619-6b9d-f34ff8351161
Version Independent ID: 844afdcd-eabb-1b6b-1130-2ff377b2c71f
Content: Understanding your Azure Cosmos DB bill
Content Source: articles/cosmos-db/understand-your-bill.md
Service: cosmos-db
GitHub Login: @rimman
Microsoft Alias: rimman

@bigdatamoore Thank you for bringing this to our attention. I am investigating this and will have an update for you shortly.

Hi @Mike-Ubezzi-MSFT, below is the response I got when I emailed the<EMAIL_ADDRESS>mailbox.  So the answer is that billing is for any portion of a wall-clock hour, not a 60 minute duration.
David,

You will be billed for the peak provisioned throughput within an hour. So in your example, you will be billed for 1,000RUs for 2 hours.

With Cosmos DB, you can scale up or down as you need and pay only for what you need. With on-premises or IaaS-hosted systems, you can't match this model, because there isn't a way to decommission the hardware every hour.

Please let me know if there is anything else you need.

Thanks,
Rimma

@bigdatamoore Thank you for this additional detail. Can you include the example you were seeking clarification for and for which a response was provided. I will include this in the doc as the examples provided in the doc doesn't see to answer a very simple billing rate question.

I will just use the example provided in your question stated above. Thank you!

I have assigned the issue to the content author to evaluate/edit/merge pull request as desired.

Ack. Please proceed. It's a little bit redundant since all cloud services with hourly billing operate in this manner, (not just on Azure but also in other clouds), but if we think this will help deflect  some questions and doubts, it's fine. Please merge. thank you.

@bigdatamoore We added a minor note to the document that will be published shortly. We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


added support for the Switch Value Instruction

Added support for Select Value Instruction

@mmroz could you please resolve the merge conflicts on this PR?


Fixes Firefox rendering issue

For some reason, Firefox has a hard cutoff of any text being rendered beyond 205px width. This small patch fixes this.

Thanks!


Integrate you publish the Airflow structure in https://github.com/Ali-Maq/aqi to https://github.com/AQ-AI/openaq-engine

The structure of the airflow is quite different from the openaq-pipeline
From what I can see the following:
### processing

buffer_processor.py

this doesnt need to exist if we are handling through earth engine (the resolution of the image is the buffer by default)

feature_extractor.py

I am assuming this is where we do the satellites

feature_merger.py

is this where we combine the field data from the satellites (e.g. with regardstot he lookback used)?

vrt_creator.py

We are not using vrt at the moment. But this is an option for when we only query from our local data store.

authentication

openaq_auth.py

when in airflow will these happen?

earth_engine_auth.py

this authentication might need to happen for every earth engine query. so the two auth processes my be executed at different times in the pipeline.

extraction

gadm_extractor.py

At the moment we arent using city-masks to extract features, although this is a possibility (combining with local file storage and vrt)

geo_location_generator.py

not sure what this does? is this generation for the prediction locations? In the first version the random points we used just for model testing, in the deployed models, we will need to sample from a grid of the agreed-upon spatial resolution.

openaq_extractor.py

is this time splitter +cohort filter + cohort builder?

TASK for today September 19 2023
##Processing :

Buffer processing - If this is happening on the google earth engine, Then I am removing this
Yes this is where we do the the ee_data.py thing to get the satellite data
regards to????  I don't get this, Yes this is where we get the satellite data and I am using the image collection method both in parallel and series in th existing pipeline
I will remove this and change the workflow.

*- Working on Google credentials generation and will share it with you @ChristinaLast , Should I just push the changes in the config file?

Can I see what is the mlflow error , so I can run and try to fix it


Nanohttpd for java1.1

nanohttpd-for-java1.1 is a permanent branch, not supposed to be merged into master


add ip for client-server interactions so that we could have more info…

… in the future to use

Coverage increased (+0.09%) to 44.54% when pulling fd0f2ca42ae912fe0d949eff3ff649629a8ea52c on nobodyiam:log-client-ip into 64a1d15bfeb78d88f05fc69a00ddeac0361459b7 on ctripcorp:master.


Enabling Shopify Build Pipeline: opencensus-service

Enabling the Shopify Build Pipeline: opencensus-service
This PR adds Shopify Build to this repository.
Please review this PR before merging it!

[ ] Head over to the Shopify Build documentation to learn more about configurating it.
[ ] Examine your shipit.yml configuration file as it may be configured to depend on the CircleCI status. You can reference a pipeline in the shipit.yml file by using buildkite/opencensus-service as seen here.
[ ] Don't forget to replace your old CI badge with the Shopify Build one. You can get it here.
[ ] If you are using codecov.io for code coverage, you'll need to add the CODECOV_TOKEN environment variable to your Shopify Build pipeline. The token can be found at codecov and should be placed in the environment section of the .shopify-build/secrets.ejson file. More info.
[ ] Rebase and squash the commits into one and don't forget to remove the [ci skip] part from the commit message:
git rebase -i 73558e6c42b145a03d28d1f712d9cfd1d06438db
[ ] We disabled commit statuses on new PRs for your pipeline to prevent other branches from being blocked while you are setting up Shopify Build. See the builds for your opencensus-service pipeline.

Cleanup After Merging

[ ] Enable commit statuses for the PRs in your repository by running (You will have to rerun your builds to start seeing them):
spy build status yes opencensus-service.
[ ] After merging the changes to set up Shopify Build you can remove CircleCI from your project by running spy circle remove Shopify/opencensus-service.
[ ] Let people know with branches that are behind the master branch that their PRs are failing, because they are missing the necessary configuration files. You can use the following reply: “We migrated this repository from CircleCI to Shopify Build. Your build is failing, because your branch doesn't include the necessary configuration files. The configuration files are missing because your branch is behind the master branch. You should rebase your branch to make the build pass with git pull --rebase origin master”

Questions about this PR?
Join the #shopify-build Slack channel.
Annoyed by how much you have to do yourself? Make it better in spy.

@fbogsany feel free to review now.
Things

rebased with master
required force to build the container, I'll follow up with shopify-build but not a huge deal
skipped a few "flakey" tests, I imagine there's others and will continue to be a problem.
it's using a custom dockerfile to facilitate our build system, they aren't doing anything exciting

we should probably not use FROM scratch, it makes debugging really hard. though not impossible
lets do that when I do the "proper" receiver


mujoco_up  with  "distutils.errors.CompileError: .......failed with exit code 2"  "distutils.errors.DistutilsExecError:"

Hi,
I'm a student and I'm trying to use MuJoCo for doing reinforcement learning in robotics
I'm looking for some help with the question as stated in the question
After I installed the "mujoco_py",when I import this package, this problem occurred:

mujoco_py is a third-party package that we do not support, and that project is now dormant. Can you use the mujoco package instead?

mujoco_py is a third-party package that we do not support, and that project is now dormant. Can you use the mujoco package instead?

Thank you for your answer. I will try your suggestion


publish defective app in pipeline: non-descriptive error raised

Describe the issue
When installing apps in a pipeline with one of those defects described, the pipeline terminates with an non-descriptive error:
WARNING: UnhandledErrorMessage
The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'.
at <ScriptBlock>, <No file>: line 39

The actual error can be one of those two:

app extends a table and uses a field id that has already been defined by another app
app extends an enum with an id, that has been already defined by another app

In both cases publishing from VS Code surfaces the correct error.
Expected behaviour
The actual publishing error makes it to the pipeline output.

In the next version I have fixed the issue when publishing via DevEndpoint - that it always says: Unprocessibly Entity - now it will display the error reason. I think however that in this case you are not using dev endpoint.
I cannot repro the issue. When I try, I get:
Publish-BcContainerApp -containerName bingmaps-ci -appFile "C:\Users\freddyk\Documents\AL\ALProject8\Default publisher3_ALProject83_<IP_ADDRESS>.app" -install -sync -skipVerification
Publishing C:\ProgramData\BcContainerHelper\Extensions\bingmaps-ci\_Default publisher3_ALProject83_<IP_ADDRESS>.app
Synchronizing ALProject83 on tenant default
Installing ALProject83 on tenant default
The field ID '50100' can only appear once in the table 'Customer'. The field is declared in multiple apps with IDs: '37a86068-0bde-4261-bf81-23b5f47b85af', '27a86068-0bde-4261-bf81-
23b5f47b85af'.

which is very descriptive.
If you still have the issue, please provide a repro scenario - maybe two .app files I can try to publish and see the error (including artifact url used).
Thanks

Thanks for taking a look!
Between me reporting this and You investigating we have had a CU update and a major update of the al compiler - maybe that changed it.
I will close this issue and open a new one IF this ever resurfaces.


[RFC] API Versioning

Addresses #242
I will delete this PR and submit a proper one shortly,  but I wanted a quick review by @almahmoud to verify this is what you have in mind.  Once I am able to bend Kubernetes and Helm to my will I can do some proper testing under the various Kubernetes versions (or at least I think I will...)

It doesn't quite work for me locally. Could it be the dry run?
~/work/galaxy-helm/galaxy(ksuderman-242-api-versioning ✗) kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:23:52Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2-rc2+k3s1", GitCommit:"d38505b124c92bffd45f6e0654adb9371cae9610", GitTreeState:"clean", BuildDate:"2020-09-18T17:34:53Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}

~/work/galaxy-helm/galaxy(ksuderman-242-api-versioning ✗) helm version
version.BuildInfo{Version:"v3.5.3", GitCommit:"041ce5a2c17a58be0fcd5f5e16fb3e7e95fea622", GitTreeState:"dirty", GoVersion:"go1.15.8"}

~/work/galaxy-helm/galaxy(ksuderman-242-api-versioning ✗) helm install --dry-run --debug test .
install.go:173: [debug] Original chart version: ""
install.go:190: [debug] CHART PATH: /Users/nuwan/work/galaxy-helm/galaxy

Error: template: galaxy/templates/priorityclass-job.yaml:8:5: executing "galaxy/templates/priorityclass-job.yaml" at <fail "This chart requires Kubernetes v1.14 or later">: error calling fail: This chart requires Kubernetes v1.14 or later
helm.go:81: [debug] template: galaxy/templates/priorityclass-job.yaml:8:5: executing "galaxy/templates/priorityclass-job.yaml" at <fail "This chart requires Kubernetes v1.14 or later">: error calling fail: This chart requires Kubernetes v1.14 or later

Looks like that's not the reason either:
~/work/galaxy-helm/galaxy(ksuderman-242-api-versioning ✗) helm install  test .
Error: template: galaxy/templates/priorityclass-job.yaml:8:5: executing "galaxy/templates/priorityclass-job.yaml" at <fail "This chart requires Kubernetes v1.14 or later">: error calling fail: This chart requires Kubernetes v1.14 or later

Thanks @ksuderman This fixes the deployments and works as expected.


Account required should be checked when skipping signature verification in join_splits

The join_split circuit now skips signature verification for merge join_splits since It checks that the spender and total amounts are going to remain the same and that only note aggregation is happening.
However, using the account_required flag an exploiter that has control over an account key but no spending keys could still drain the notes that have account_required to true:

Decode the notes using the account key
Do regular merge join_splits with them, with a fake signature (since it's going to be skipped) to the same owner BUT creating the output notes as account_required = false
Now the attacker can spend the notes with the account key since the output notes are account_required false

Great catch

Closed by #70


Added doc to PSP

Regarding this issue, already solved
https://github.com/okteto/app/issues/4994

@mnevadom could you create a branch release-1.2 and send the PR against it?

@mnevadom could you create a branch release-1.2 and send the PR against it?

Done


Add a System Maintenance Guide

Add an SMG to the documents folder, it only needs to be an initial document with the general page structure. The main part will be to start writing about how to set up a development environment.
Acceptance Criteria

[x] A new SMG exists in the documents folder in the code base.
[x] There are details in the SMG about how to set up a development environment.

Added a small section in the SMG, under 03, pointing to the tile server script page so local data can be initialised

All acceptance criteria met.
An SMG document is saved in the code base at:  docs\SMG. It contains full details about how to set up a development environment and will continue to evolve as the project progresses.


Not all changed files staged and committed

I have an issue where bumpver doesn't stage and commit all of the changes it has made. As best I can tell, it fails when there is capital letters in a folder name on the path to a file.
Reproduction steps:

Fetch https://github.com/SRFU-NN/test_bumpver/tree/main/src (minimal example)
Create a virtual environment
Install bumpver version 2023.1125
Run bumpver update --patch

Expected results:
All 4 copies of test.txt have updated version, and are included in the tagged commit.
Actual result:
Three copies of test.txt has updated version and are included in the tagged commit.
src\CaPiTaLiZaTiOn\test.txt has updated version, but is not staged.
Environment:
Windows 10 Enterprise, Version 10.0.19044 Build 19044
Python 3.9.4
bumpver version 2023.1125

Thank you for this report. I imagine this is a duplicate of #204.

Yes, I've closed it. If you can help to figure out how to fix this, I'd greatly appreciate it.

A quick test indicates that pathlib does not have the same issue as pathlib2 – though I know going to an unsupported package is not a good idea.
I will investigate some more.
Best regards
Søren Furbo
Automation Scientist
7660 Automation and Process Optimisation
+45 3079 0427 (direct) ǀ<EMAIL_ADDRESS>From: mbarkhau @.>
Sent: 8. august 2023 13:12
To: mbarkhau/bumpver @.>
Cc: SRFU (Søren Furbo) @.>; Author @.>
Subject: Re: [mbarkhau/bumpver] Not all changed files staged and committed (Issue #218)
Caution: This email originated from outside of the Novo Nordisk email system. Use caution when clicking on links or opening attachments.
Yes, I've closed it. If you can help to figure out how to fix this, I'd greatly appreciate it.
—
Reply to this email directly, view it on GitHubhttps://github.com/mbarkhau/bumpver/issues/218#issuecomment-1669413749, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AY4V7XOZKS35KWQ4RZETR2DXUINGZANCNFSM6AAAAAA3G7NBPU.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

I have created an issue in pathlib2: https://github.com/jazzband/pathlib2/issues/86

@SRFU-NN I'd like to somehow test the changes in PR #219. Since we don't have windows in our CI system, perhaps you can help with this? Can you review PR #219 ?

@SRFU-NN I'd like to somehow test the changes in PR #219. Since we don't have windows in our CI system, perhaps you can help with this? Can you review PR #219 ?

I'll look into it.


Convert kube-apiserver to hyperkube

Part of #108.
Also:

Added hyperkube cmd (not built by default yet).
Added version support to hyperkube
Remove health_check_minions flag from apiserver as it is no longer used with #3733

I'm running e2e tests now.  This is a pretty simple refactor though (in theory).

pkg/apiserver/server/server.go should be under pkg/master.
apiserver is general api infrastructure, used by openshift, and will be used by kubelet, also.
master is the kubernetes api server.
I didn't diff cmd/kube-apiserver/apiserver.go and pkg/apiserver/server/server.go. I assume you did. :-)
Probably should give a heads up to @smarterclayton.

FWIW, the Openshift instantiation of the master is here:
https://github.com/openshift/origin/blob/69b94514166d9b3cf2a212f6ebd65ff8d7066d2c/pkg/cmd/server/start.go#L459

@bgrant0607 -- PTAL -- moved it to pkg/master/server.  I'm also watching all changes to cmd/apiserver to make sure I don't miss any merges.

Hyperkube, excellent name.  Looking

Works for me, if it's ok with @smarterclayton. I figure we can fix/tweak it as necessary after the initial refactor goes in.

Looks good to me but don't consider it authoritative.

Ok. Will merge when tests complete.


gddo: redirect to HTTPS

You can visit content at http://godoc.org, but I think we should redirect all traffic from that domain to https://godoc.org. There are lots of reasons to want privacy while browsing godoc.org depending on the software you are reading about.

gddo bug tracker is https://github.com/golang/gddo/issues

Whoops, this is a dupe of golang/gddo#493.


Tweak coverage reporting

generate cover file in same directory as files being tested
use codecov action (the bash uploaded is deprecated)

Signed-off-by: Scott Andrews<EMAIL_ADDRESS>

Rebased to fix a conflict


Fix bug #2 - comments using "-" instead of "--"

When merged, line comments will be correctly handled by comment/uncomment line command (Ctrl+/). Fixes #2.

Thanks!

Thanks for making this extension! I'd love to see this bugfix included in the next release (1.0.6?).


Model own Scheduler Architecture

Model the implemented Nexus Architecture as Class and Activity Diagram
Linked ticket: https://github.com/valentin-carl/nuclio/issues/19

lgtm


chore: refactor collectibles UI to UI package

Try out Leather build 5e1c0a1 — Extension build, Test report, Storybook, Chromatic

When working on the native collectibles code, I decided to migrate similar UI components from the extension to the monorepo.

This is stale, I'll pick it up again


travis: Use bionic, no sudo and python 3.6

switch to Ubuntu Bionic to have a recent version for testing
Do not use sudo. That will switch from VMs to containers which
improves build speed on travis a lot
use python3.6 . python2 is EOL

Signed-off-by: Thomas Bechtold<EMAIL_ADDRESS>

Travis is disabled again. Seems to be super slow...


Scan OCI Containers

Takes a resource, currently this can only be a registry. It downloads each layer to memory and then extracts to the clonepath.
Still left to do:

Tests.
Implement local container: Need to research how these are normally stored. I have only see tar files without layers. Understanding others use cases for local might be useful.
See if there are more cases where it will fail. For example, the registry might send .tar files without compression. the mediaType in the manifest should provide information.
Consider mounting the gzip layers to a file system. I think the current way of extracting to disk is the best, this can be to a ram based tmpfs if disk usage is an issue. Mounting it to a FS would probably complicate the code more and make cross platform a bit harder.

From the gosec errors, only number 2 should even be exploitable at the moment.
1 - Potential file inclusion - should be mitigated by not extracting files with .. in the name - thought maybe we can just remove the .. from the name and extract that way (if it ever comes up).
2 - decompression bomb - We could set a max file size of 30MB or similar. Most that size in containers are going to be binaries that we don't scan anyway. The other option is that the max size is 10x the size of the layer blob, or similar. Easy enough to implement.
3 - Similar to 1 and should be mitigated the same way.
[/github/workspace/pkg/resource/container.go:158] - G304 (CWE-22): Potential file inclusion via variable (Confidence: HIGH, Severity: MEDIUM)
    157:
  > 158: 		file, err := os.OpenFile(path, os.O_CREATE|os.O_TRUNC|os.O_WRONLY, 0600)
    159: 		if err != nil {

[/github/workspace/pkg/resource/container.go:164] - G110 (CWE-409): Potential DoS vulnerability via decompression bomb (Confidence: MEDIUM, Severity: MEDIUM)
    163:
  > 164: 		_, err = io.Copy(file, tarReader)
    165: 		if err != nil {

[/github/workspace/pkg/resource/container.go:149] - G305 (CWE-22): File traversal when extracting zip/tar archive (Confidence: HIGH, Severity: MEDIUM)
    148: 		}
  > 149: 		path := filepath.Join(r.clonePath, header.Name)
    150: 		info := header.FileInfo()

G110

Going to do the following with a layer size  * 10 and add logging so it can be reviewed. Unlikely a file with decent data will have a compression >10 and be the only file in the layer.
		_, err = io.CopyN(file, tarReader, size)
		if err != nil && err != io.EOF {
			logger.Error("Error copying file to disk: %v", err)
			return err
		}

@bplaxco I have answered/actioned all the comments, except leveraging other resources walks within this one. I'll need to sit down and figure that out.
I'd like to get this in soon-ish so I can start working on revamping errors which will be a very noisy change.

Looks good to me. I added a couple of small things but if you change those no need for another MR.
Also I think there's a few things in the README that could be touched up:

the priority option for the container kind
I think a todo called out
And personal preference: "fake-leaks\\base64-encoded", -> "fake-leaks/base64-encoded",

Anywho, merge when ready! :D

Does this scan manifest metadata (layer commands, environment variables, etc.) in addition to layer content? :eyes:


Upgrade from 3.3 to 3.4 theme issue

When upgrading from 3.3 to 3.4 I ran into the issue with the default paper theme still using JsValidator in places see here (line 15): https://github.com/cnvs/paper/blob/master/resources/views/auth/login.blade.php I was using a custom theme I forked from the default paper theme, but when I went to the source I see the latest commit is still using it. To get around this I referenced the dark paper theme and was able to get it working, so its just an FYI.
Btw thanks for building this repo so far I'm really liking it and looking forward to what goodies might be coming out with the 5.4 release.

Thanks for the kind words @blueyama! The themes have undergone a bit of changing since you last forked, and JSValidator was one of the items that got removed due to an upgrade issue with the package. Here is the changelog entry.
And you're right to keep your eye out for the next release, it'll take care of a number of bugs and bring the app up to speed with Laravel 5.4 👍

I'm keeping an eye out for the next release 💯
Ah indeed, I missed the fact that the cnvs/easel repo had the paper theme views prepackaged with it. I guess this would only effect the people who have forked from the paper theme. I'm guessing the two repos should be even:
https://github.com/cnvs/paper/blob/master/resources/views/auth/login.blade.php
https://github.com/cnvs/easel/blob/master/resources/views/auth/login.blade.php

Yes you're right they should be even. Organizing and refactoring the themes is another task for the next release so we don't run into these issues anymore.


Issue with bigint primary key and forceEntityConstructor

Describe the bug
There appears to be an issue when using forceEntityConstructor on entities which have collections that use bigint for their primary key.
The issue happens when retrieving the parent object and loading it's collection.  It seems like each object in the collection is trying to be parsed as a bigint and this caues the error:
 SyntaxError: Cannot convert [object Object] to a BigInt
        at BigInt (<anonymous>)

      at BigIntType.convertToJSValue (node_modules/@mikro-orm/core/types/BigIntType.js:32:24)
      at node_modules/@mikro-orm/core/entity/EntityFactory.js:308:62
          at Array.map (<anonymous>)
      at EntityFactory.extractConstructorParams (node_modules/@mikro-orm/core/entity/EntityFactory.js:278:39)
      at EntityFactory.createEntity (node_modules/@mikro-orm/core/entity/EntityFactory.js:193:33)
      at EntityFactory.create (node_modules/@mikro-orm/core/entity/EntityFactory.js:58:39)
      at SqlEntityManager.find (node_modules/@mikro-orm/core/EntityManager.js:152:45)
      at Object.<anonymous> (src/example.test.ts:75:17)

Outline of the reproduction
@Entity()
export class User {
  // Unrealistic example, but it's just to show use case of forceEntityConstructor
  private role = "ADMIN";

  @PrimaryKey()
  id!: bigint;

  @Enum()
  name!: string;

  @OneToMany(() => UserComments, (x) => x.user)
  comments = new Collection<UserComments>(this);

  constructor(props: Pick<User, "name">) {
    this.name = props.name;
  }

  getRole() {
    return this.role;
  }
}

@Entity()
export class UserComments {
  @PrimaryKey()
  id!: bigint; // change to number to fix the issue

  @ManyToOne(() => User)
  user!: User;

  @Property()
  text!: string;
}

let orm: MikroORM;

beforeAll(async () => {
  orm = await MikroORM.init({
    dbName: ":memory:",
    entities: [User, UserComments],
    debug: ["query", "query-params"],
    forceEntityConstructor: true,
    allowGlobalContext: true,
  });
  await orm.schema.refreshDatabase();
});

afterAll(async () => {
  await orm.close(true);
});

test("can load entity with bigint pk and access private variables", async () => {
  const user = new User({ name: "John Doe" });

  const comment = new UserComments();
  comment.text = "a comment";
  user.comments.add(comment);

  await orm.em.persistAndFlush(user);
  orm.em.clear();

  // error : SyntaxError: Cannot convert [object Object] to a BigInt
  const users = await orm.em.findAll(User, { populate: ["comments"] });
  expect(users[0].getRole()).toBe("ADMIN");
});

Reproduction
https://github.com/cpt-pete/mikro-orm-bigint-bug/
What driver are you using?
@mikro-orm/sqlite
MikroORM version
6.3.11
Node.js version
20
Operating system
macos
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord.
[X] The provided reproduction is a minimal reproducible example of the bug.

Speedy work! Thanks


Add an email client

For finishing off a user registration.

This is fixed by e57f7425bd1dd783e517ce4da652042ce180aa24.  I eventually chose to use HaskellNet-SSL which seems to work well with gmail SMTP.  I had no joy with either smtp-mail which I think doesn't support TLS encryption or with the gmx mail server.


Add  ss58 prefix 88 for Aurgon Network (chongya.com)

Added ss58 prefix for https://chongya.com Aurgon Netwrok
Prefix  88, likes doesn't collide with other prefixes.
I've added this prefix to files:
ss58-registry.json
primitives/core/src/crypto.rs
Hope everything is ok.

User @webguo, please sign the CLA here.

Signed, thx.


Established guidelines for End user system

Description
Established guideline  for end-user systems for how they should integrate with Altinn 3 ifb with the submission of data.
Additional Information
No response
Tasks
No response
Acceptance Criterias
No response

https://docs.altinn.studio/api/guides/endusersystems/
The guideline has been created and QA has been carried out for those who will use it.


reintegrate doc components from dotland

a bunch of things are broken right now, and the showcase needs to be updated


Spanner add back partitioned DML support

fixes #1709
adds partitioned DML back to spanner

uh oh, let me do some rebase...

@dmitry-s @meltsufin merged, ready for review PTAL


Zoom to Tapped Area

Changes proposed in this pull request:

Zoom to the tapped area

@jsahoo Thank you for the PR, it looks super clean ;)


VSR: Fix allocation size of parse_addresses() return value

The Allocator interface requires the exact length of the allocation to be provided when freeing memory. With the current implementation, there is no correct way to free the returned slice.

Therefore, would you please change this to use something like mem.count() on the number of commas, so that we allocate exactly without the shrink?

Done, StaticAllocator seems like a neat idea :)

Do the tests need to be updated at all for this? Is there any coverage that could be added?

I had to tweak one test due to a slight change in the order of errors reported since we now check the limit before checking that the addresses are valid.
I also just added one positive test case that explicitly tests when the number of provided addresses is less than the limit. I don't see any other missing edge cases in the tests.


Implement Stats Tracker

Backend requirements:

Track and provide in the API:

How many times a user has bought cards (checked out from the Checkout) - "Purchases"
How many sales the user has done (orders). - "Sales"
Sales this month - "Sales This Month"
Average rating from reviews - "Seller Rating"
How many times has the seller rejected a sale. - "Rejection Rate"
How many times has the seller not sent a sale. - "Miss Rate"

Frontend requirements:

Display the correct information in the User Profile section.

I have a question about the last point:

How many times has the seller not sent a sale. - "Miss Rate"

Currently, for an order status, we only save if it's rejected for whatever the reason is, both from the seller and buyer,
I can figure out a way to check how many times the seller rejected but I am not sure how to check with the current setup if he missed to sent, since there is only a status rejected.

Can you please check my logic and advise if you agree that we can count it like that,

How many times has the seller rejected a sale. - "Rejection Rate" -> a rejection rate will be counted if the seller after status ordered immediately rejected the order.

How many times has the seller not sent a sale. - "Miss Rate" -> miss rate will be counted if the seller sent the order but the buyer marked it as not received.

Yes
No. There is the possibility that a seller can just literally not send a package (ghost the buyer). So if the seller does not send the package in 7 days, we should mark the order as "not sent".

I understand, that makes sense now. Thanks! 🙌


GlossyCarPaint and MatteCarPaint are too specific

GlossyCarPaint and MatteCarPaint appearances are slightly used in other contexts.
They are basically a flat surface painted with a glossy or matte paint. Or metallized paint?
I propose to simply remove the "Car" keyword from their names.
@all Is it ok like this, or do you have better propositions?

It seems to refer to paint on a metallic or bodywork surface, which may be different from a wooden or plastic surface... Why not replacing "Car" with "Bodywork"?

From the definitions I found, Bodywork seems to be related to vehicles only, but these appearances should be much more generic.

I think that the matter (if it's flat and without defaults) behind the paint does not affect much the final rendering if the paint cover it perfectly (which is the case here).

Ok, then, I am fine to remove the "Car" word as initially proposed by @fabienrohrer.

👍
Ok, I will go forward like this.

CarLeather suffers from the same issue.

Same problem, same solution 😄

Fixed in #277


[pegtl] Update from v3.2.2 to v3.2.5

Describe the pull request

What does your PR fix?

Bumps the version of PEGTL from 3.2.2 to 3.2.5, which includes a fix for a static_assert with recent versions of MSVC that breaks the build of the cppgraphqlgen port.

Which triplets are supported/not supported?

Yes.

Yes.
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

It looks like the PR validation failed because it couldn't install the 7zip MSI it downloaded.

@wravery Looks like there is a problem with the CI test, I will re-request the test and identify the problem. :)

Oh, I remembered, our CI is being upgraded recently, it may take a few more requests to pass, I will take care of this。


Move tempest/clock to tempest/support

This is really too small a package to be an individual component

I'm gonna leave it for now…


Update assign-pod-node.md

updated some of the lines making it a bit easier to read and understand !

/lgtm

I agree with @divya-mohan0209 's comment that the grammatical changes in this PR are not needed

@r0ushann please rebase

@r0ushann : This has been pending action for nearly a long time without updates. We’ll be closing this PR. Kindly reopen it once you’re ready to action on the suggestions.


Syncing latest changes from upstream devel for ceph-csi

PR containing the latest commits from upstream devel branch

/approve

/lgtm

/cherrypick release-4.18


Permanent progress bar not working on XP Tracker Overlay

I've tried messing around with the fade out and time until disappear settings, but I can't get the progress bar to stay up permanently like the vanilla XP tracker.

Did you try to set time until disappearance to 0 under xp tracker settings

@Norkotah was the suggestion by l2- sufficient? Following up on this issue as it's pretty stale. I can look into it if setting the value to 0 doesn't work, otherwise this issue can likely be closed.


Add event watcher

Watch event local network issue (gateway is unreachable)
Watch event global network issue (mail server is unreachable)
Add power supply instability issues

I've created new issue - #18 (power loss is not actual because whole lab was supplied through UPS)


fix: uid corrupted when run envd by root user

Signed-off-by: Qi Chen<EMAIL_ADDRESS>

It is a workaound for root users.
We need a better design for envd user and its use in image building and user use.

@aseaday Hi, is this PR ready to review?

@aseaday Hi, is this PR ready to review?

I need do some tests in conda install and different shell use. Later today.

No hurry. Thanks!
Please at me @gaocegege  if it is ready to review.

PTAL

@all-contributors Please add @aseaday for the code contribution.


[test] workflows

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Close because done with testing


feat: clear tenant's cache on update or delete

Is there a reason you're doing those inspects everywhere? Seems odd idk.

I use inspect() to make valid map's key/value pairs, and then it will be possible to safely encode them to JSON.


Explanation

Hi,
I'm currently trying to get it working on a XMC 4500 Relax Kit, because I have to use an Infineon controller for my Bachelor Thesis. My current problem is, that I always get a negative angle between -1.2 and -1.3°.
So could you please explain the formular for the angle. Right now I don't really get all of it completely.

Negative angle in general is fine; it just means that the sensor is to the left of center line (if it's a horizontal sweep).
What is the range of timings you get? Maybe the problem is in the timing module or the unit conversion?
The formula itself should be quite simple: angle = (time_in_microsec - 4000) * PI / 8333.3

Here is a OneDrive link to the data I get. I fear that the code I use to get the time intervals is wrong.
https://1drv.ms/u/s!At2vyt_CVX2WlwpsfbrrJKduDgek
//calculate lenght of the sync pulse
i[0] = last_signal_period;
i[1] = last_signal_duty;
sync_pulse = (i[0] - (i[1] / 100 * i[0])) / 1000;
//sync pulse decoding
if(decode())
{
	angle =(i[0] / 1000 - 4000) * M_PI / 8333;
 }
I'll write a new code today with another methode to get the timings.

Yeah the timings seem wrong. Too much variation. Be sure to calculate timing from the beginning of sync pulse to the center of the laser sweep cycle.
One more thing - you're getting angle in radians, not degrees.

Could it be, that it just won't work with only one Lighthouse Box?

I got my hands on an oscilloscope. I get some really weird pulses out of my sensors. I think, that my Lighthouse Box searchs for the second one, which is simply not there.

Did you manage to make it work? I'm wondering what the issue was.

No I'm still struggling. Is it possible that it won't work without a second box?

Yeah, it won't work with just one box. Two needed for a 3d fix. Are you trying to get it running without a full HTC Vive set? It might be possible to get the angles with two stations, but if you want to get xyz position, then you'll somehow need to get their position and rotation very precisely, which I don't know how to do without the full set.

Just saw you asked this question a month ago, which I missed, sorry for that!

Hi Alex, I just saw your first Alpha release.  Congratulations!  I'll give it a try later this week.
The release comment says, "(almost) everything is configurable and users can just upload the .hex file"
Is that because we still need to run SteamVR, calibrate the room using Vive's calibration, and copy/paste the matrices to the sensor?

Thanks All! This is the wrong thread for this conversation, though :) don't
be afraid to create a new issue to discuss it.
As for your question - yes, we need base station geometry from steamvr, but
also how many sensors, objects, what format, where to stream, etc. See
small example in src/settings.cpp.
On Feb 20, 2017 11:05 AM, "Al B"<EMAIL_ADDRESS>wrote:
Hi Alex, I just saw your first Alpha release. Congratulations! I'll give it
a try later this week.
The release comment says, "(almost) everything is configurable and users
can just upload the .hex file"
Is that because we still need to run SteamVR, calibrate the room using
Vive's calibration, and copy/paste the matrices to the sensor?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ashtuchkin/vive-diy-position-sensor/issues/9#issuecomment-281159144,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmVHdcJLrXob8mwT2C_B-L39wugzhHQks5reeP0gaJpZM4LdbF0
.

Hello,
@Bloodline95 Did you determine what was causing your unexpected oscilloscope readings?  I'm also getting something similar.  I'm using one lighthouse (no sync cable), in mode A, and here are my readings:

Well shoot, the sensor was too close to the lighthouse.  We pulled it back to ~3 feet and that fixed it.


Production Build Getting 404 Error When Refresh Page

Hi all,
I'm getting the error with production build when I reload page as below:

I already changed config in uglify like this:

But it's still not working
Can you help me to fix this issue? Thanks!

Hi,
I changed "useHash:true" and It's working properly.


VideoStreaming with RtmpDisplay works only with small resolution

Hello. I use your RtmpDisplay solution as plugin for my Unity3D application to stream my game view, cameraView and microphone. It works fine with 320x240 streaming resolution and I can receive streaming video and audio result with my vlc-player for example. But if I change streaming resolution to 640x480 then on my vlc-player I receive only first several seconds of streaming video and audio and after that video stops and I receive only audio from microphone. I tried three different rtmp-servers with same result. How can I fix this? Does this depends of FPS of my Unity game? Thanks.

Btw, If I change to RtspDisplay video and audio streaming works fine with any resolution. Maybe that matters for any answer...

Can you check if video packets stop send in device log when you use rtmp?
If you can try this:

Force software video encoder to discard rtmp module bug with your encoder (add this line after create RtmpDisplay class):

rtmpDisplay.setForce(CodecUtil.Force.SOFTWARE, CodecUtil.Force.FIRST_COMPATIBLE_FOUND);

If this solve your problem let me know device model, API and encoder used that fail for you.
Maybe de error is that your encoder create a bad header after some seconds in high resolution. In rtsp module I'm not doing h264 header check and this could be the problem.

@pedroSG94 Thanks for the answer. Force software video encode doesn't solve my problem.
Video packets doesn't stop send in both cases.

Which server and player are you using?
Can you try change both to discard problems with that side?

Tried node-rtsp-rtmp-server from wiki. Same result: Rtsp works great, Rtmp stops showing video after several seconds on standard vlc application.

Changed player to Live Stream Player, connected to node-rtsp-rtmp-server and Rtmp started working normal. Strange that VLC player have such problems

Is this closed now? @DoPinG83 we are building a plugin too for unity3d. How was your overall experience?


Bugfix reused validators#122

Adresses #122

Codecov Report

Merging #136 (6d30290) into main (0d1863b) will decrease coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #136      +/-   ##
==========================================
- Coverage   96.71%   96.60%   -0.12%
==========================================
  Files          12       12
  Lines        1006     1032      +26
==========================================
+ Hits          973      997      +24
- Misses         33       35       +2

Impacted Files
Coverage Δ

.../autodoc_pydantic/directives/options/composites.py
97.61% <ø> (-0.06%)
:arrow_down:

.../autodoc_pydantic/directives/options/definition.py
100.00% <ø> (ø)

sphinxcontrib/autodoc_pydantic/__init__.py
100.00% <100.00%> (ø)

...rib/autodoc_pydantic/directives/autodocumenters.py
99.02% <100.00%> (+0.08%)
:arrow_up:

sphinxcontrib/autodoc_pydantic/inspection.py
98.63% <100.00%> (-0.02%)
:arrow_down:

...xcontrib/autodoc_pydantic/directives/directives.py
96.46% <0.00%> (-1.77%)
:arrow_down:

Continue to review full report at Codecov.

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


The entire project becomes impossible to compile directly (as of Aug, 2022).

Upgrading Swift 3 to 4 requires Xcode 10.1, according to warnings given by Xcode 13 and 14.
Xcode 10.1 requires macOS Mojave. Recent macs aren't able to run this version of macOS.
I have tried using VMware. It went kernel panic everytime trying to unzip the Xcode installation package (an XIP file).
Also, I tried install Cocoapods on macOS Mojave, and it asks that Ruby must >= a specific version (maybe 2.5 if my memory is correct).

I managed to extract the Xcode through macOS recovery mode, and it was succeeded.
However, looks like homebrew already deprecated support of Xcode 10.1.


Adding Release GitHub Action

This PR introduces a GitHub Action to publish Nautobot python packages to GitHub and PyPi as well as build and push the docker containers.  I added a slack notification as well which we can customize or remove as needed.  Also, I need someone on the core team to validate the secrets we are using here and let me know if I need to change them.

This might be a bit premature with https://github.com/nautobot/nautobot/pull/1184 on the way but I figure this is the best we have now and matches the current process.


[UPGRADE] Upgrade of PgBouncer [Kubernetes]

Is your feature request related to a problem? Please describe.
We need to upgrade PgBouncer if possible and needed to the newer version. This task should be done after we will upgrade PostgreSQL to v13.
This task applies to K8s application
Describe the solution you'd like
We want to upgrade if possible and needed to the newer version of PgBouncer.
Describe alternatives you've considered
None.
Additional context
This task should be done after upgrade of PostgreSQL to v13.

DoD checklist

[ ] Changelog updated
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Idempotency tested
[ ] Documentation added / updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license

We are currently using PgBouncer v1.10.
As for now the latest available is v1.15.0.
Need to update OS packages and docker image for application deployment on kubernetes.

This tasks basically includes two different tasks:

Upgrade and configuration pgbouncer as a k8s instance
Upgrade and configuration pgbouncer installed directly on database hosts as standalone application. In this case Python  dependency is needed (blocker by #2334)

This might be good to split this task up to two different ones.

PR #2462

:heavy_check_mark: New installations have been tested, as well as the upgrade from v1.12. I've also deployed a sample application on k8s with psql and connected via pgbouncer to postgresql without any problems.