can someone explain --nth and --with-nth. It (seemingly?) does not behave as documented.

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[x] bash
[ ] zsh
[ ] fish

Problem / Steps to reproduce
Can someone explain --nth and --with-nth as it does not seem to work as documented, or I totally don't understand it. I read several issues on this topic, still have no clue, why it behaves like this.

--n-th

-n, --nth=N[,..]
Comma-separated  list  of  field  index expressions for limiting
search scope.  See FIELD INDEX EXPRESSION for the details.
echo "1,2,3,4,5" | fzf -d "," --nth 1 --> single selection 1,2,3,4,5
echo "1,2,3,4,5" | fzf -d "," --nth 2 --> single selection 1,2,3,4,5
echo "1,2,3,4,5" | fzf -d "," --nth 2,3 --> single selection 1,2,3,4,5
echo "1,2,3,4,5" | fzf -d "," --nth 666 --> single selection 1,2,3,4,5
should this behave like this?
--with-nth
echo "1,2,3,4,5" | fzf -d "," --with-nth "2" --> single selection 2,
echo "1,2,3,4,5" | fzf -d "," --with-nth "2..3" --> single selection 2,3,
if comma is delimiter, why it's part of output??? I understood, that it was said somewhere that delimiter is regex and not single char as explanation, but I don't understand how is this relevant. It was also explained that this is intended for simple cases only, where I asked for single column, but this is my case actually, I want only single column without delimiter.
IIUC documentation correctly, command:
echo "1,2,3,4,5" | fzf -d "," --with-nth "-2" should return single selection of 4.
If not, what it should return and why is delimiter not behaving like delimiter? If this is valid, I think the documentation should give explanation what is expected to be returned and why.
If there is know workaround, please suggest. tr ',' ' ' is not sufficient, as this causes information loss or expected expensive tr ' ' '<forbiddenSymbol>' | tr ',' ' ' | fzf ... | tr ' ' ',' | tr '<forbiddenSymbol>' ' '

@LangLangBart Thanks for the detailed answer.

--nth doesn't affect how the items are displayed inside fzf. It only affects the search scope.

if comma is delimiter, why it's part of output???

--with-nth can be used to reorder the columns.
echo "1,2,3,4,5" | fzf -d "," --with-nth 2,1,5
  # Prints "2,1,5"

In this case, we can't simply remove the delimiters. One would argue that we can just put , characters between the tokens, but we can't take the same strategy when --delimiter is specified as a regular expression.
I know the situation is not ideal, but I couldn't find a better solution that doesn't complicate the option or break the backward compatibility.
Anyway, pre-processing the list gives you the most flexibility.
# Use awk to preprocess the input while retaining the original text before the tab character
# Use --with-nth not to display the original text before the tab character
echo "1,2,3,4,5" | awk -F, -v OFS=, '{print $0 "\t" $3, $1, $2}' | fzf -d "\t" --with-nth 2.. --bind 'enter:become:echo {1}'


member.setVoiceChannel not working

Please describe the problem you are having in as much detail as possible:
The member.setVoiceChannel method doesn't appear to work.
When called, it throws TypeError: Converting circular structure to JSON and after a while throws Error: socket hang up and crashes.
Include a reproducible code sample here, if possible:
import { Client } from 'discord.js'
const client = new Client()

client.on('message', message => {
  if (message.content === 'test') {
    console.log('hi')
    const channel = message.guild.channels.find('name', 'voicechannel')
    message.member.setVoiceChannel(channel)
  }
})

client.login('xxx')

Further details:

discord.js version: 11.1

node.js version: v7.4.0

Operating system: Windows 10

Priority this issue should have – please be realistic and elaborate if possible: medium, library does not have support for moving guild members to different channels with this broken.

[x] I have also tested the issue on latest master, commit hash:
f95f18b586069bb40ebe027c4a014a0263190641

Fixed in ff822970 and e3c3a4fd respectively.


Codegen: don't use init flag for string constants

Also includes a small refacor.
For example if you have code like this:
puts FOO

FOO = "hello"

Then before this PR when reading FOO we would check whether it was initialized or not. This is not needed before a string literal doesn't need a special initialization, it's just data.
Like with #9801, it's not common to find code like the above but it is common that this happens because of order of require and the way the compiler works.
Benchmark (Int#to_s uses some constants that are string literals):
require "benchmark"

null = File.open(File::NULL, "w")

Benchmark.ips do |x|
  x.report("Int#to_s") do
    123456789.to_s(null)
  end
end

Before:
Int#to_s  89.91M ( 11.12ns) (± 4.98%)  0.0B/op

After:
Int#to_s  97.35M ( 10.27ns) (± 5.22%)  0.0B/op  fastest

Oh, it's failing with the Crystal constants which aren't in the program's AST. I'll fix that later.

@asterite can you rebase on master?

Sure! Just note that you can also do it because the branch is in this repo 😉

Done!


home-assistant: support idasen_desk component

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 337793 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.idasen_desk
python311Packages.idasen-ha
python311Packages.idasen-ha.dist
python312Packages.idasen-ha
python312Packages.idasen-ha.dist


Make Standard SQL Default

Heya!
In the new BigQuery UI Google is rolling out standard SQL as the default for queries, I am wondering if we can do the same with operations using this package?
This is a small connivance but it gets me every time.
Thanks!

It is a breaking change so we’ll want to communicate it widely, but I’m supportive of this proposal.

Shall we:

Change default to None and warn on None that future versions will have Standard SQL default
In a later version change the default to Standard

@RafaelAMello if you agree, would you be interested in creating a PR?

Yup happy to do it,
Should I implement something like the verbose warning depreciation?
When do you think it's best then change the default parameter to standard?
Thanks!

Great, something like warnings.warn(msg, FutureWarning) would work.
If @tswast agrees, I think we change the default in 0.6, assuming that's a few months away?
If someone upgrades past the warning, their code will obviously break rather than return an incorrect result (although won't be clear why it broke) so it's bad but not disastrous.

Change default to None and warn on None that future versions will have Standard SQL default
In a later version change the default to Standard

Sounds like a good plan to me.

Let's leave this open to track changing the default; the warning is merged, courtesy of @tswast
(should we do a release with this?)

I actually made a release last week. https://pypi.org/project/pandas-gbq/0.6.0/ I forgot to add the release info to GitHub, though. I'll do that now.

Great, thanks!

Now that we have the pandas_gbq.context object (#208), we could add a dialect property to the context object to allow people to pick their own defaults, as suggested in #103.
To start out, we could populate the default with 'legacy' and switch to 'standard' in a few months.

We need to update the samples at https://pandas-gbq.readthedocs.io/en/latest/reading.html to show an explicit dialect.

Good point @tswast
We could also change the default now?

Now that #235 is in and released as part of 0.8 it is possible for people to change the default dialect back to legacy if they really need to. We can now change the default to standard SQL.


fix the job calculation in data cache

Beginning pylint and unit tests.
See https://cmssdt.cern.ch/jenkins/job/DMWM-PR-test/202/ for details

Summary of pylint changes for pull request 6104:

Score for src/python/WMCore/WMStats/CherryPyThreads/CherryPyPeriodicTask.py decreased from 8.36 to 7.50
Errors for src/python/WMCore/WMStats/CherryPyThreads/CherryPyPeriodicTask.py increased from 1 to 2
Warnings for src/python/WMCore/WMStats/CherryPyThreads/CherryPyPeriodicTask.py increased from 6 to 7

src/python/WMCore/WMStats/CherryPyThreads/CherryPyPeriodicTask.py fails the pylint check. Report follows:

Line 26 in CherryPyPeriodicTask.init W0212 Access to a protected member _internal_name of a client class
Line 31 in CherryPyPeriodicTask.setConcurrentTasks W0613 Unused argument 'config'
Line 12 in CherryPyPeriodicTask R0903 Too few public methods (1/2)
Line 40 in CherryPyPeriodicTask.setConcurrentTasks W0201 Attribute 'concurrentTasks' defined outside init
Line 58 in PeriodicWorker.init W0702 No exception type(s) specified
Line 78 in PeriodicWorker.run W0703 Catching too general exception Exception
Line 97 in SequentialTaskBase.call E1101 Instance of 'SequentialTaskBase' has no '_callSequence' member
Line 100 in SequentialTaskBase.call W0703 Catching too general exception Exception
Line 103 in SequentialTaskBase.call E1101 Instance of 'SequentialTaskBase' has no 'logger' member
Line 88 in SequentialTaskBase R0903 Too few public methods (1/2)
Line 120 in DataUploadTask.setCallSequence W0201 Attribute '_callSequence' defined outside init
Line 88 in SequentialTaskBase R0922 Abstract class is only referenced 1 times
plus 43 comments on code style

src/python/WMCore/WMStats/Service/ActiveRequestJobInfo.py fails the pylint check. Report follows:

Line 29 in ActiveRequestJobInfo.validate W0613 Unused argument 'apiobj'
Line 29 in ActiveRequestJobInfo.validate W0613 Unused argument 'api'
Line 29 in ActiveRequestJobInfo.validate W0613 Unused argument 'safe'
Line 30 in ActiveRequestJobInfo.validate W0612 Unused variable 'args_length'
Line 29 in ActiveRequestJobInfo.validate W0613 Unused argument 'method'
Line 29 in ActiveRequestJobInfo.validate R0201 Method could be a function
Line 8 W0611 Unused import logging
Line 9 W0611 Unused import cherrypy
plus 14 comments on code style

No changes to unit tests for pull request 6104

Beginning pylint and unit tests.
See https://cmssdt.cern.ch/jenkins/job/DMWM-PR-test/203/ for details

Summary of pylint changes for pull request 6104:

Score for src/python/WMCore/WMStats/CherryPyThreads/CherryPyPeriodicTask.py decreased from 8.36 to 7.50
Errors for src/python/WMCore/WMStats/CherryPyThreads/CherryPyPeriodicTask.py increased from 1 to 2
Warnings for src/python/WMCore/WMStats/CherryPyThreads/CherryPyPeriodicTask.py increased from 6 to 7

src/python/WMCore/WMStats/CherryPyThreads/CherryPyPeriodicTask.py fails the pylint check. Report follows:

Line 26 in CherryPyPeriodicTask.init W0212 Access to a protected member _internal_name of a client class
Line 31 in CherryPyPeriodicTask.setConcurrentTasks W0613 Unused argument 'config'
Line 12 in CherryPyPeriodicTask R0903 Too few public methods (1/2)
Line 40 in CherryPyPeriodicTask.setConcurrentTasks W0201 Attribute 'concurrentTasks' defined outside init
Line 58 in PeriodicWorker.init W0702 No exception type(s) specified
Line 78 in PeriodicWorker.run W0703 Catching too general exception Exception
Line 97 in SequentialTaskBase.call E1101 Instance of 'SequentialTaskBase' has no '_callSequence' member
Line 100 in SequentialTaskBase.call W0703 Catching too general exception Exception
Line 103 in SequentialTaskBase.call E1101 Instance of 'SequentialTaskBase' has no 'logger' member
Line 88 in SequentialTaskBase R0903 Too few public methods (1/2)
Line 120 in DataUploadTask.setCallSequence W0201 Attribute '_callSequence' defined outside init
Line 88 in SequentialTaskBase R0922 Abstract class is only referenced 1 times
plus 43 comments on code style

src/python/WMCore/WMStats/Service/ActiveRequestJobInfo.py fails the pylint check. Report follows:

Line 29 in ActiveRequestJobInfo.validate W0613 Unused argument 'apiobj'
Line 29 in ActiveRequestJobInfo.validate W0613 Unused argument 'api'
Line 29 in ActiveRequestJobInfo.validate W0613 Unused argument 'safe'
Line 30 in ActiveRequestJobInfo.validate W0612 Unused variable 'args_length'
Line 29 in ActiveRequestJobInfo.validate W0613 Unused argument 'method'
Line 29 in ActiveRequestJobInfo.validate R0201 Method could be a function
Line 8 W0611 Unused import logging
Line 9 W0611 Unused import cherrypy
plus 14 comments on code style

No changes to unit tests for pull request 6104


wine{Unstable,Staging}: 6.1 -> 6.2

Motivation for this change
New upstream version.
My usual Wine programs seem to work fine with the new staging.
@avnik
Things done

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

[x] NixOS
[ ] 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 nixpkgs-review --run "nixpkgs-review wip"
[ ] 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
[ ] Fits CONTRIBUTING.md.

@robbert-vdh Mentioned that wine 6.2 will break building yabridge.

I get:
builder for '/nix/store/wbfvyqlb17wak6b4c2ij5ad5n8nvhvjc-wine-6.2-staging.drv' failed with exit code 2; last 10 log lines:
  tools/winebuild/winebuild -w --def -o dlls/wmvcore/libwmvcore.def --export dlls/wmvcore/wmvcore.spec
  tools/winebuild/winebuild -w --def -o dlls/wsdapi/libwsdapi.def --export dlls/wsdapi/wsdapi.spec
  tools/winebuild/winebuild -w --def -o dlls/wsnmp32/libwsnmp32.def --export dlls/wsnmp32/wsnmp32.spec
  tools/winebuild/winebuild -w --def -o dlls/mswsock/libmswsock.def --export dlls/mswsock/mswsock.spec
  tools/winebuild/winebuild -w --def -o dlls/wtsapi32/libwtsapi32.def --export dlls/wtsapi32/wtsapi32.spec
  tools/winebuild/winebuild -w --def -o dlls/x3daudio1_7/libx3daudio1_7.def --export dlls/x3daudio1_7/x3daudio1_7.spec
  tools/sfnt2fon/sfnt2fon -q -o fonts/coue1255.fon fonts/courier.ttf -d 128 13,1255,8
  Error: Cannot open face fonts/courier.ttf
  make: *** [Makefile:149640: fonts/coue1255.fon] Error 1
  make: *** Waiting for unfinished jobs....

@veprbl Hmm, that's weird. I was able to successfully build it rebased against the latest commit the nixos-unstable: ff96a0fa5635770390b184ae74debea75c3fd534.

I just ran nixpkgs-review

Can't reproduce now. Must be a transient error.


Feature/dcmfoss 67 copy2

Description

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

Is this the same as "Feature/dcmfoss 67 copy"? Please use more unique PR titles ;-)
Please resolve merge conflict.

Is this the same as "Feature/dcmfoss 67 copy"? Please use more unique PR titles ;-)
Please resolve merge conflict.

@carslen  I have closed the other similar pull requests and that due to a problem on the used username which caused issues in the checks to fail.
So Could you review this pull requests? I have resolved the conflicts.

Please monitor open pull requests actively. I'm going to handle the PRs chronologically.


cilium-operator: only GC identities of its own cluster

Proposal / RFE
Problem statement
With kvstore (etcd) as identity allocator, cilium-operator is responsible for garbage collecting the identity master keys (cilium/states/identites/v1/id/<id>). If multiple cilium clusters share a same kvstore (not a usual case, and should be avoided in most scenarios), there would be race conditions as multiple cilium-operators try to GC the same set of master keys.
Describe the solution you'd like
cilium-operator of each cluster only GCs the master keys of its own cluster.
This information is already available as ClusterID is configured for each cilium-operator, with which we could calculate the identity range of this cluster. Then, we can distinguish the keys by the valid identity range.
Other aspects

Compatibility: compatible with the upstream.
GC Performance downgrade: neglectable.
Stakeholding: it would benefit another draft proposal.

We'd like to contribute a patch if this proposal (issue) is approved. Thanks!

For your reference: a draft PR is created in #16825. Thanks!

Reopening given the PR with the fix was reverted in master.


Reorg

Start of Makefile for exploring reorg_dist.
Note that for the modules we are bringing in (only libpysal and esda for exploration at the moment) we have to haul their package folders up one level after cloning. This works but I'm wondering if there are going to be problems induced here?
We could punt on the source redistribution and just rely on pip to install the dependencies (i.e., libpysal, esda, spint.......)? In this case the makefile could be used for setting up a local dev environment, while the dependences remain outside of the pysal/pysal upstream repository? Food for thought.
Also added a setup.py for the metapackage.  This would have pip do the heaving lifting on dependencies - pysal becomes a lightweight metapackage.

test failures look like an issue in the libpysal API.

Coverage decreased (-83.06%) to 0.0% when pulling 5b74a7e8c6c19eaf30dc6e2f24afab244bd412c5 on sjsrey:reorg into 3fb707352a8da4861df1c22de54fc7353c9c05ed on pysal:reorg.

Coverage decreased (-83.06%) to 0.0% when pulling fa0a128498ca1411547025a441bf1cad696ea063 on sjsrey:reorg into 3fb707352a8da4861df1c22de54fc7353c9c05ed on pysal:reorg.

Coverage decreased (-83.06%) to 0.0% when pulling 8e5e1ee8fbd31df9a785866c3e92c10be31236b8 on sjsrey:reorg into 3fb707352a8da4861df1c22de54fc7353c9c05ed on pysal:reorg.

Coverage increased (+6.2%) to 89.286% when pulling 3adaa70a7e7b2df596511a871d4bb6a300283a2a on sjsrey:reorg into 3fb707352a8da4861df1c22de54fc7353c9c05ed on pysal:reorg.


Join names

sqlalchemy was raising warnings and you couldn't actually access the left and right sides any more.

looks like dask is complaining about some stuff, did anything change here recently?

dask is changing fairly rapidly these days
ping @mrocklin

ok this dask stuff is blocking, taking care of it now

very small issue .... going to push directly to master

fixed in 376d87b

sorry ... your whatsnew conflicts with the one i just merged in :|

rebased, does the change look correct, if so I will merge on pass.


Fix: updated co.generate docstring

The function docstring was saying that the truncate argument was "END" on default, but actually it is None.
This PR fixes this error in the docstring.

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


fix/devtools panel displaying on Firefox

* Please fill in the required items.

Priority*

[x] High: This PR needs to be merged first for other tasks.
[ ] Middle: This PR should be merged quickly to prevent conflicts due to common changes. (default)
[ ] Low: This PR does not affect other tasks, so it can be merged later.

Purpose of the PR*
Fix displaying devtools panel on Firefox
Changes*
[FOR FILL]
How to check the feature
Open 'devtools' option in devtools panel(sidebar) on Firefox

@Jonghakseo I was opened it to create first small step to fix this issue


Support for Server-to-Client events

This PR adds support for MEGA's server-to-client events.
This allows to maintain the local node tree (the Nodes struct) up-to-date, even as the remote tree changes by asking MEGA about the what changed since the time of our last fetch and applying the deltas on our own local tree.
Here is an example of how to make use of some of this new feature:
// This is our initial fetch of nodes from MEGA:
let mut nodes = mega.fetch_own_nodes().await?;
//  ^^^ notice how `nodes` is now mutable, since we'll be updating it later.

// Some time passes ...

// We fetch to see if there is some new node events from MEGA since our last update:
if let Some(batch) = mega.poll_events(&nodes).await? {
    // Some events were delivered to us !

    // We can inspect them, if we are expecting something specific:
    for event in batch.events() {
        Event::NodeCreated { nodes } => {
            // New nodes were created !
            // `nodes` is of type `Vec<EventNode>`.
            todo!()
        }
        Event::NodeUpdated { attrs } => {
            // A node's attributes have been updated !
            // `attrs` is of type `EventNodeAttributes`.
            todo!()
        }
        Event::NodeDeleted { handle } => {
            // A node has been deleted !
            // `handle` is of type `String`.
            todo!()
        }
    }

    // We can then apply these events to our local node tree to bring it up-to-date with MEGA's servers:
    nodes.apply_events(batch)?;
}

// We can also indefinitely (and efficiently) wait for at least one MEGA event to be delivered:
let batch = mega.wait_events(&nodes).await?;

Checks are implemented to make sure events are applied in the correct order.
This is done using a event sequence identifier that MEGA itself delivers with each batch of events.
It should therefore be impossible for Nodes to diverge from MEGA's remote (up-to-date) tree.
The worst the local Nodes can be from MEGA's tree is being out-of-date, but never wrongly updated due to skipped events or out-of-order application of events.

This feature seems ready to be merged, especially now that it has some tests for it.


Albion boss in Lapis Manalis - wrong callout?

When the boss is casting his slams the prompts are calling out the danger zones instead of the safe zones.
This is from the perspective of being in front of boss where it is currently looking.
Are you expecting everyone to be behind the boss since he moves towards the entrance and are looking towards the entrance of boss area?
As a tank i always do the reverse for the prompts and the prompts for the slams always get me hit since its double reversed on the slams.

Left/right calls are boss relative so they are consistent.  "Left" means "go to the boss's left flank" and "right" means "go to the boss's right flank".  It is always relative to the boss.  The only real exception is for wall bosses where players are always facing the boss, and so "left" means "go to your left (facing the boss)", e.g. p8s and p12s final bosses.

What do you mean exactly with boss relative?  cause the bos is looking my way and the callouts are wrong in that position

But if the hole party is in front  of boss wont boss relative apply there too? or does it mean boss relative from middle of boss room? The callouts assume that the party is in the middle of the boss room

The boss has a left arm and a right arm.  It doesn't matter where you are facing him from, left always means boss's left, i.e., the side of the boss's left arm.  We do not track player position relative to the boss/arena or make calls that are player relative.

The boss has a left arm and a right arm. It doesn't matter where you are facing him from, left always means boss's left, i.e., the side of the boss's left arm. We do not track player position relative to the boss/arena or make calls that are player relative.

But with that logic you would be getting hit by the p12 boss from the wings since it would be calling out the same as what's being cast. the boss has a right wing and a left wing but it still is calling out the reverse.

doesn't matter where you are facing him from, left always means boss's left
so if left is always left then i should be taking the left side of the p12 boss when he cast the spell on his left wing?

It works exactly like the P12 boss; when the boss is cleaving the right side, the callout says left, as in the boss's left.  It makes no attempt to adjust for player facing.  when Albion (the Lapis Manalis first boss) uses Right Slam, it calls left, regardless of player facing.

i think i get it twisted since he turns around

Sorry for the confusion.  I understand what you're asking for and why this doesn't work for you specifically, but I think in general it would cause more confusion if it were not consistent about what "left" meant.  (Imagine this example, boss facing north, two players standing west, one slightly north of west and one slightly south of west; do you call left for one and right for the other?)
For the sake of cactbot triggers, I think it's better to just always call left-meaning-left-flank so that players always know what calls mean, and the calls are the same for everybody.


vimPlugins.presence-nvim: init at 2021-06-08

Things done

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

[X] NixOS
[ ] 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 nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

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

[X] Fits CONTRIBUTING.md.

And please add a motivation, the template is there for a reason.

Sorry about that! Added the motivation in the comment and also renamed the commit message!


End of parameter name with a dot

router.Get("/account/:id.json", handler)

params.ByName("id")

Right now the parameter names end with a slash or the end of the path, how about if the dot also means the end of the parameter?

I actually considered this before, but it is a bit complicated. In contrast to slashes, not every dot separates path segments, which makes the matching a lot more difficult.

I have a working version of httprouter with this change, but the code is difficult to understand, so I am not sure what I just changed:
https://github.com/gin-gonic/httprouter/commit/2ecb7ac21a43e5f3e7041826e53dc007a102e397
what do you think? what could fail?

I know dots do not separate path segments, but nobody is going to use a parameter name with dots, so in my opinion it makes sense to understand a dot as the end of the parameter name.

See my comment on your commit

Additionally, something like router.Get("/account/:id.:filetype", handler) could be extremely convenient.

we'd love to have this feature too :+1:

@julienschmidt sorry I just saw your comment in my commit.
you are right, this is not trivial

@squirkle well, I would not overload the router that much. if you want the extension just do this:
extension := filepath.Ext(filename)

@manucorporat is it necessary to create an endpoint for each filetype or is it possible to allow a route to accept multiple filetypes?
example:
route /report will not match /report.json or /report.csv as it ends searching before it gets to the file extension
I could, however, create multiple routes with all the file extensions desired. Thoughts?


Bugfix/lld/remove extra data track

📝 Description
Remove extra track in account and parentAccount attribute for button_clicked (swap/stake/receive)
❓ Context

Impacted projects:  LLD
Linked resource(s):  https://ledgerhq.atlassian.net/browse/LIVE-6886

✅ Checklist

[ ] Test coverage
[ ] Atomic delivery
[ ] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

/update-screenshots


[FEATURE REQ] GitHub shouldn't allow to merge to master if CI failed

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ ] Description Added
[ ] Expected solution specified

I have permissions to the repo... just need to flip configs


Client filters researcher

This pull request is the start of the shared filter logic for the Dataset Browser and the Researcher.

I have created a Zustand store in the new 'list-store' package.
I have refactored the client-filters component, so it uses the list store and removed dataset-specific logic (mainly the filters).
I have moved one function of lib/search-params (getUrlWithSearchParams) to the store. The other functions are more project-specific and may need to be moved, but this takes more time.
I have duplicated the UI components for the Researcher app.

Nest steps, out of scope for this pull request:
I want to refactor the client-filters component and his children and move to the UI package.

Use the store in all components instead of passing down the state. Logic can also move to the store, leaving only UI in the client components.
Change to compound components with dot notation. With compound components, it is easier to have UI differences in the apps.

Not working after the 'Next' upgrade to 13.3.1.  For some reason, the initialization in client-list-store.tsx  is not going correctly which results in falling end-to-end tests. After typing in the query field, the query will reset with an old value. This does not happen with 13.2.4.


[reconciler] Use buffered channels

Related: https://github.com/coinbase/rosetta-sdk-go/pull/187
This PR changes the rosetta-cli to use buffered channels for the reconciler.
Changes

[x] update rosetta-sdk-go
[x] only exit reconciliation coverage end condition if last index is greater than min (protects against buffered channel backlog)

If Heimdall is stuck, please click the following link: https://heimdall-public.cbhq.net/v1/pull_request/stuck?pr_number=163&repository=coinbase/rosetta-cli


Release 0.10

What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

merged


'liveView' is deprecated in Playground Pages

I get the following error when trying to build and run the playgrounds in the project in Xcode 8.2:
warning: 'liveView' is deprecated: Use 'PlaygroundPage.current.liveView' from the 'PlaygroundSupport' module instead
Is this expected?

we just upgraded everything to xcode 8.3 and swift 3.1, which has a lot of fixes for playgrounds. so please try master on the newest xcode


vendir succeeds when includePath list item does not exist?

imho this is a bug, but I'm asking first in case this is a "functions as designed". If it is functioning as designed, then might I humbly request that design be revisited.
I have a config which is similar to what is shown below (git repos are different)
---
apiVersion: vendir.k14s.io/v1alpha1
kind: Config
directories:
- path: .vendir
  contents:
    - path: service
      git:
        url: git@github.com:org/software.git
        ref: 40ef6a
      includePaths:
        - k8s/modules/base/*
        - this/*
        - does/not/exist/*

I can guarantee that there are files in the first list item (the k8s path). The other two paths I made up.
When I run vendir sync, the output that I get is
Fetching: .vendir + service (git from git@github.com:org/software.git@40ef6a)

  --> git init
 ...bunch of git command output here...

Lock config

apiVersion: vendir.k14s.io/v1alpha1
directories:
- contents:
  - git:
      commitTitle: 'fix: remove sharder annotations'
      sha: 40ef6a85a4fa84a23a0193db9ea2773ba3b5614e
    path: service
  path: .vendir
kind: LockConfig

Succeeded

I can verify this is successful with the output of $? as well
$ echo $?
0

Is this expected behavior?
If so, I think this can very likely lead to some (bad) unintended consequences. The worst being that the end-user trusts that vendir will arrange some files correctly, when it actually doesn't.
For example, consider kubernetes manifests via ytt being vendir'd. Due to "reasons" (network hiccup, fat fingered path, path not existing at a particular version, etc) the paths include invalid paths. vendir produces a set of files and ignores the paths it couldn't find. k8s app gets deployed without a subset of content. The world spirals into chaos.
Thoughts?

@caphrim007 currently that's intentional behaviour.

Due to "reasons" (network hiccup, fat fingered path, path not existing at a particular version, etc) the paths include invalid paths. vendir produces a set of files and ignores the paths it couldn't find

network hiccup would result in a much earlier failure at asset download time. includePaths/excludePaths are filters are all has been successfully downloaded.
making a mistake is definitely a possibility though. i dont think we can change default behaviour at this point; but, ill have to think about how to enhance this feature to provide you with extra safety. (globs are typically meant to represent 0+, but in your case, you really want 1+.)


Switch displacement vertex vectors back to arrays

Used vectors for easier debugging of index out of range errors instead of generating a heap corruption

Added in 1af2ff824d26c915f8a25bc511ee4d35d52d277d


[Feature Request] Export/Import Block List

Explain in detail what your suggested feature would be used for.
A simple export/import of your block list in different file formats.
Describe how it would look if it requires a UI.
N/A
Explain why people would want to use it.
For people who want a fresh start without the bullshit of drama starters, problematic people, etc. This is an easy way to just transfer from one account to another.

Bulk moderation is a bit tricky, and from my foggy memory about it, is something VRChat isn't fond of. From what was discussed in the discord, it being something that can affect someone's trust ranking, also doesn't help.

PLEASE ADD THIS! IT IS SO IMPORTANT!

omg, o h my god. Most needed feature, they refuse to add. THis is laughable

we are not inclined to add features you request, VRCX is a free application, if you want this feature add it yourself.

sure, I go spent hundrets of hours into learning how to program just so I can add this block/mute list ex/importer, even thought u could just add it in a couple minutes. sure....

omg, o h my god. Most needed feature, they refuse to add. THis is laughable

who are you

at this point I think it's just fear of the vrx developers. They are scared they program might be moderated or something by the vrchat team. Absoloute  cowardish

sure, I go spent hundrets of hours into learning how to program just so I can add this block/mute list ex/importer, even thought u could just add it in a couple minutes. sure....

Here you go, have fun.
app.js

omg, o h my god. Most needed feature, they refuse to add. THis is laughable

u guys should retire, if u cant even make a block/mute list import/export mechanic

at this point I think it's just fear of the vrx developers. They are scared their program might be moderated or something by the vrchat team. Absoloute cowardish. I doubt they ever do anything daring!

Hi, VRCX team has direct communication to VRChat's staff they routinely talk with us since VRCX has reached a large amount of users. this is not assumptions VRChat has asked us in the past to make changes to VRCX and expressed displeasure in adding the feature automated moderation, we are not adding the feature for this reason.

communicate with them again, stop being a coward. VRchat staff must think they got u on the balls at this point

u guys should retire, if u cant even make a block/mute list import/export mechanic

You’re welcome to fork the VRCX project and implement this feature yourself if you’d like. However, the maintainers have decided not to include this feature, as it can be easily abused and may put its users at risk of being flagged for moderation. Thank you for understanding.

I'm speechless.

I hope you're just a troll at this point

From what was discussed in the discord, it being something that can affect someone's trust ranking, also doesn't help.

This is a complete invalid statement, since they can simply add a warning message to the use of this feature, so everyone can decide for himself if he wants to make use of it or not.

From what was discussed in the discord, it being something that can affect someone's trust ranking, also doesn't help.

so everyone can decide for himself if he wants to make use of it or not.

It's not just about an individual deciding whether they want to use it. The main concern is that simply having an abusable mass-moderation system within the program would be enough of a red flag for VRChat to take action against VRCX and its users. Either way, VRChat would likely instruct the maintainers to remove it, and they would, of course, comply. We’re sorry, but we don’t intend to drag the application's users down due to a lack of foresight on your part.
Again, if you want this functionality, consider learning to code, forking the project, and implementing it yourself.

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

applying moderation's against any users affects their rank such as blocking and muting, VRChat is very much against this and any sort of automated moderation's can be abused or used in a targeted manor (KOS Lists) thus why VRChat has expressed a dislike in the idea in the past.

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

The original post states.

Explain in detail what your suggested feature would be used for.
A simple export/import of your block list in different file formats.

Keyword being 'file formats'. I really shouldn't have to spell this out for you.

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

VRCX can't just transfer the entirety of your blocks, it has to re-do every block individually one by one, which is spammy especially if you have a lot of blocks. :p

To put it simply for you

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

Simply put, users could create KOS lists from this if the blocks and mutes lists were made exportable and importable as file formats. This would also place a heavy load on their servers due to the high volume of API calls resulting from user moderation actions occurring simultaneously.

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

applying moderation's against any users affects their rank such as blocking and muting, VRChat is very much against this and any sort of automated moderation's can be abused or used in a targeted manor (KOS Lists) thus why VRChat has expressed a dislike in the idea in the past.

I could simply reblock everyone, that would also affect their rank. But why when it can be achieved in a better way. If I really wanna hurt a user, I make 100 accounts, and block on all of these accounts a certain user.
What u say makes 0 sense again.

To put it simply for you

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

Simply put, users could create KOS lists from this if the blocks and mutes lists were made exportable and importable as file formats. This would also place a heavy load on their servers due to the high volume of API calls resulting from user moderation actions occurring simultaneously.

the issue ur describing here isnt an importer tool, but creating mass accounts

To put it simply for you

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

Simply put, users could create KOS lists from this if the blocks and mutes lists were made exportable and importable as file formats. This would also place a heavy load on their servers due to the high volume of API calls resulting from user moderation actions occurring simultaneously.

this isnt even remotely possible

It's simple math really.
Easier to use = more usage
A single block from you is nothing, but a block list circulating is potentially several hundred of users blocking the same person

let them block.  Is their loss

For what it's worth, VRCX also already has a high support volume. Giving users a footgun will eventually cause users to trickle in that managed to shoot themselves, it's practically in the best interest of nobody.

To put it simply for you

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

Simply put, users could create KOS lists from this if the blocks and mutes lists were made exportable and importable as file formats. This would also place a heavy load on their servers due to the high volume of API calls resulting from user moderation actions occurring simultaneously.

this isnt even remotely possible

In your other responses, you mention that you don’t understand and that it makes no sense to you, yet you’re telling me this isn’t even remotely possible?

To put it simply for you

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

Simply put, users could create KOS lists from this if the blocks and mutes lists were made exportable and importable as file formats. This would also place a heavy load on their servers due to the high volume of API calls resulting from user moderation actions occurring simultaneously.

this isnt even remotely possible

In your other responses, you mention that you don’t understand and that it makes no sense to you, yet you’re telling me this isn’t even remotely possible?

No point creating KOS list, when u can make one of ur own and import

No point creating KOS list, when u can make one of ur own and import

so you can implement the feature yourself? great, looking forward to the pull request. cheers!

I know u guys can

I'll do it for you, cashapp me $100

how is this abuse?  Nothiung u've staied or these other guys said remotely make any sense.

applying moderation's against any users affects their rank such as blocking and muting, VRChat is very much against this and any sort of automated moderation's can be abused or used in a targeted manor (KOS Lists) thus why VRChat has expressed a dislike in the idea in the past.

I could simply reblock everyone, that would also affect their rank. But why when it can be achieved in a better way. If I really wanna hurt a user, I make 100 accounts, and block on all of these accounts a certain user. But who would do that>?! What u say makes 0 sense again.

so you're telling me that if someone made a list of hundreds of known pedos, crashers and racists you wouldn't think "Wow I should import that and keep myself away from all these people." so what happens when even 30% of the VRCX users use this to block all those people? millions of API calls from vrcx (and their API already looks for blocking users in short succession when you could target crash someone with a client by blocking everyone in the lobby but your target and change into the crasher then out of it before unblocking everyone so this is an 11/10 way to get banned lmao.) also "who would do that" You must not have ever met a client user before. Their ultimate goal is to go around crashing people they don't like (AKA the people on this list that could be spread around) and you get a notification when someone who's blocked or muted joins so it's implementing the KOS list without any other work. you would just upload this list of mutes and you don't even have to unblock them to crash them. the fact that you know nothing about vrcx the API or even the player base and are so adamant about how something is "the most important feature" is pretty crazy. if you really want this here are some options.

fork vrcx and make it yourself. you can use chatGTP for a lot these days and it might not take as long as you think to do something like this just use the vrcx source code from here on GitHub and the API documentation on https://vrchatapi.github.io

pay someone to do it. things like Fiver igist for a reason or I'm sure just about any client creator will make it for you if you pay them enough. ( you better run every anti-virus on the planet lmao this is a joke)

make a discord or GitHub repo where you put all of the User IDs of anyone that you've blocked/muted and share that or keep it for your next account? Idk why this is useful anyway unless you make new accounts or share the list but.

use the (currently broken URI (u r i) links such as vrcx://user/usr_ID to make some sort of script to do it for you in autohotkey or some other macro program (again or pay someone to do this) this is probably your best bet for price or time but if you are trying to share this good luck finding anyone who will run your program that basically needs some sort of access to there account lmao.

TLDR; uhhhhh you don't know what you're talking about, it's bad for your account, bad for vrcx, bad for vrchat, and bad for the community. we don't need EAC update for the API lol. I have given you some options on how to proceed if you wanted to.

Just a note, the user was already blocked from the repo, no point in engaging them any further.


Ember Use in Docs Over Blaze

Working on the g8 template now

Talked it over a bit, and the strategy is to document Ember alongside Blaze in 0.21, and make it the default in 0.22.
This should achieve the latter, so retargeting.

This hung our docs build.  Some backend didn't shut down somewhere.

It looks like this one is already going south in client.md.  It would be great to get this one landed, because the g8 template is already cut over.

Didn't make it into the 0.22 docs, but superseded by https://github.com/http4s/http4s/pull/5970 in the 0.23 docs.


Uncaught SyntaxError: Unexpected token /

[Enter steps to reproduce below:]

...
...

Atom Version: 1.7.4
System: Mac OS X 10.11.3
Thrown From: amWiki package, v0.2.6
Stack Trace
Uncaught SyntaxError: Unexpected token /
At file:///Applications/Atom.app/Contents/Resources/app.asar/static/index.html#%7B%22initialPaths%22%3A%5B%22%2FUsers%2Fym%2FDesktop%2Fakwiki%22%5D%2C%22locationsToOpen%22%3A%5B%7B%22pathToOpen%22%3A%22%2FUsers%2Fym%2FDesktop%2Fakwiki%22%2C%22initialLine%22%3Anull%2C%22initialColumn%22%3Anull%2C%22forceAddToWindow%22%3Afalse%7D%5D%2C%22windowInitializationScript%22%3A%22%2FApplications%2FAtom.app%2FContents%2FResources%2Fapp.asar%2Fsrc%2Finitialize-application-window.js%22%2C%22resourcePath%22%3A%22%2FApplications%2FAtom.app%2FContents%2FResources%2Fapp.asar%22%2C%22devMode%22%3Afalse%2C%22safeMode%22%3Afalse%2C%22profileStartup%22%3Afalse%2C%22clearWindowState%22%3Afalse%2C%22env%22%3A%7B%22TMPDIR%22%3A%22%2Fvar%2Ffolders%2F48%2Fxpj64q2161qdclh_lt3yfyf40000gn%2FT%2F%22%2C%22__CF_USER_TEXT_ENCODING%22%3A%220x1F5%3A0x19%3A0x34%22%2C%22SHELL%22%3A%22%2Fbin%2Fbash%22%2C%22HOME%22%3A%22%2FUsers%2Fym%22%2C%22Apple_PubSub_Socket_Render%22%3A%22%2Fprivate%2Ftmp%2Fcom.apple.launchd.Pgpr1yaYOY%2FRender%22%2C%22SSH_AUTH_SOCK%22%3A%22%2Fprivate%2Ftmp%2Fcom.apple.launchd.BXq2nYD9ZA%2FListeners%22%2C%22PATH%22%3A%22%2Fusr%2Fbin%3A%2Fbin%3A%2Fusr%2Fsbin%3A%2Fsbin%22%2C%22LOGNAME%22%3A%22ym%22%2C%22XPC_SERVICE_NAME%22%3A%22com.github.atom.175712%22%2C%22USER%22%3A%22ym%22%2C%22XPC_FLAGS%22%3A%220x0%22%2C%22GOOGLE_API_KEY%22%3A%22AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q%22%2C%22ATOM_HOME%22%3A%22%2FUsers%2Fym%2F.atom%22%7D%2C%22appVersion%22%3A%221.7.4%22%2C%22atomHome%22%3A%22%2FUsers%2Fym%2F.atom%22%2C%22shellLoadTime%22%3A225%7D:2

SyntaxError: Unexpected token /
    at Object.parse (native)
    at Object.module.exports.buildAt (/Users/ym/.atom/packages/amWiki/lib/creator.js:77:23)
    at Object.module.exports.createWiki (/Users/ym/.atom/packages/amwiki/lib/main.coffee:68:13)
    at atom-workspace.subscriptions.add.atom.commands.add.amWiki:create (/Users/ym/.atom/packages/amwiki/lib/main.coffee:24:28)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:160:19)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (/Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:1100:28)
    at EventEmitter.outerCallback (/Applications/Atom.app/Contents/Resources/app.asar/src/application-delegate.js:314:25)
    at emitTwo (events.js:87:13)
    at EventEmitter.emit (events.js:172:7)

Commands
     -2:36.4.0 core:paste (atom-text-editor.editor.is-focused)
     -2:34.6.0 core:backspace (atom-text-editor.editor.is-focused)
     -2:33.2.0 amWiki:pasteImg (atom-text-editor.editor.is-focused)
     -2:21.1.0 editor:copy-path (atom-text-editor.editor.is-focused)
     -2:20.1.0 amWiki:pasteImg (atom-text-editor.editor.is-focused)
     -2:18.2.0 core:paste (atom-text-editor.editor.is-focused)
     -2:17.2.0 editor:delete-to-beginning-of-line (atom-text-editor.editor.is-focused)
     -2:13 amWiki:pasteImg (atom-text-editor.editor.is-focused)
     -1:30.1.0 command-palette:toggle (atom-text-editor.editor.is-focused)
 12x -1:23 core:backspace (atom-text-editor.editor.mini.is-focused)
     -1:20.5.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -1:20.5.0 core:cancel (atom-text-editor.editor.mini.is-focused)
  3x -0:50.9.0 amWiki:create (div.package-detail.panels-item)
     -0:05.8.0 tree-view:remove (span.name.icon.icon-file-text)
     -0:00.4.0 amWiki:create (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "themes": [
      "one-dark-ui",
      "material-syntax"
    ]
  }
}

Installed Packages
# User
amWiki, v0.2.6
atom-html-preview, v0.1.19
atom-ternjs, v0.14.1
atomatigit, v1.5.5
autoclose-html, v0.23.0
autocomplete-paths, v1.0.2
color-picker, v2.1.1
emmet, v2.4.3
file-icons, v1.7.12
language-babel, v2.23.0
language-diff, v0.4.0
linter, v1.11.4
linter-coffeescript, v1.0.0
linter-eslint, v7.2.2
material-syntax, v0.5.0
pigments, v0.26.3

# Dev
No dev packages

这问题应该是config.json解析失败了，需要使用json格式，现在已经增加了弹窗提示，不再报错


Adds unique sprite for NTBlockGame screen

About the PR
Original sprite was CrudeCode's but I modified it to better fit.
Sprite could probably use some work I mainly made this to demonstrate how to do it for Crude.
Screenshots

Changelog

:cl: Swept

add: Adds unique screen for NTBlockGame

Updated version of the sprite made in cooperation with /tmp/moony#0029

Updated version of the sprite made in cooperation with /tmp/moony#29

as far as i can tell this hasn't been added to the pr yet, has it?

Yea that sheet isn't in the PR at all.

also jfc clean your pr, there is some other rework in there

Wdym clean it check the commits

Modified the sprite to include the blinking at the end.

also jfc clean your pr, there is some other rework in there

Wdym clean it check the commits

nvm i had a brain moment


Fixed spelling error

"roes" to "rows"

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks


Installing OSBA on Cloud Foundry

Hi,
I am currently installing osba into my OS Cloud Foundry solution (as per these instructions: https://github.com/Azure/open-service-broker-azure/blob/master/contrib/cf/README.md) and have come across an issue when cf pushing the service broker.
I get the following error:
Staging app and tracing logs...
   Cell eb0e351d-78e4-45a3-b388-bc91ce480b81 creating container for instance 5eb1fe9c-ba21-4b54-b9ab-d7827024b10f
   Cell eb0e351d-78e4-45a3-b388-bc91ce480b81 successfully created container for instance 5eb1fe9c-ba21-4b54-b9ab-d7827024b10f
   Downloading app package...
   Downloaded app package (69.4M)
   Downloaded buildpack `https://github.com/cloudfoundry/go-buildpack/releases/download/v1.8.13/go-buildpack-v1.8.13.zip` (4.9M)
   -----> Go Buildpack version 1.8.13
   -----> Installing godep v79
          Download [https://buildpacks.cloudfoundry.org/dependencies/godep/godep-v79-linux-x64-9e37ce0f.tgz]
          Download [https://buildpacks.cloudfoundry.org/dependencies/glide/glide-v0.13.0-linux-x64-f13fe16b.tgz]
   -----> Installing dep v0.3.2
   -----> Installing go 1.8.5
          Download [https://buildpacks.cloudfoundry.org/dependencies/go/go1.8.5.linux-amd64-fe5c03fb.tar.gz]
          Note: skipping (dep ensure) due to non-empty vendor directory.
   -----> Running: go install -tags cloudfoundry -buildmode pie github.com/Azure/open-service-broker-azure/cmd/broker
   vendor/golang.org/x/crypto/scrypt/scrypt.go:13:2: cannot find package "math/bits" in any of:
        /tmp/gobuildpack.gopath255328754/.go/src/github.com/Azure/open-service-broker-azure/vendor/math/bits (vendor tree)
        /tmp/contents923048986/deps/0/go1.8.5/go/src/math/bits (from $GOROOT)
        /tmp/gobuildpack.gopath255328754/.go/src/math/bits (from $GOPATH)
          **ERROR** Unable to compile application: exit status 1
   Failed to compile droplet: Failed to run finalize script: exit status 12
   Exit status 223
   Cell eb0e351d-78e4-45a3-b388-bc91ce480b81 stopping instance 5eb1fe9c-ba21-4b54-b9ab-d7827024b10f
   Cell eb0e351d-78e4-45a3-b388-bc91ce480b81 destroying container for instance 5eb1fe9c-ba21-4b54-b9ab-d7827024b10f
Error staging application: App staging failed in the buildpack compile phase
FAILED

Is anyone able to advise?
Also I noticed the default go buildpack is behind the latest - is it as simple as this?

Yeah, I think it is probably caused the old go buildpack. Please have a try newer buildpack.

@robdickens does new buildpack work? If work, I'll update the example.

HI @zhongyi-zhang, apologies for the delay (other priorities etc..)
I updated the go buildpack version to v1.8.42 and used the latest tag of osba (v1.8.2) and everything deployed and the osba started successfully.
The one difference is the fork of go buildpacks based on cflinuxfs 2 & 3 meaning you'll need to reference either buildpack depending on your version of cloud foundry
Haven't fully tested everything yet, but it definitely gopt rid of my immediate issue so thought I'd let you know.
Thanks.

I have clone repo v1.8.4.
Update manifest.yml with vars.
██cf push -f contrib/cf/manifest.yml
....
Uploading osba...
Uploading app files from: /home/sergey/works/projects/xxx/open-service-broker-azure
Uploading 70.5M, 19654 files
Done uploading
FAILED
Error processing app files: Error uploading application.
Error: timed out waiting for async job 'https://api.sys.cf.xxx.xxx.com/v2/jobs/4f918543-476d-4758-bd2a-21f91a9b7250' to finish


Prelodr.setOptions(options) not working?

Prelodr.setOptions(options) doesn't seem to be working.
The error I'm seeing on Chrome is
VM225:1 Uncaught TypeError: pre.setOptions is not a function
    at <anonymous>:1:5

I can use pre.show(): and pre.hide(); without any problems.
const pre = Prelodr({
    prefixClass: 'prelodr',
    duration: 300
})

pre.setOptions({prefixClass: 'prelodr', duration: 300});
pre.show('loading');

I will review it..
El jue., 5 de enero de 2017 12:08, Jiho Kang<EMAIL_ADDRESS>escribió:

Prelodr.setOptions(options) doesn't seem to be working.
The error I'm seeing on Chrome is
VM225:1 Uncaught TypeError: pre.setOptions is not a function
at :1:5
I can use pre.show(): and pre.hide(); without any problems.
const pre = Prelodr({
prefixClass: 'prelodr',
duration: 300
})
pre.setOptions({prefixClass: 'prelodr', duration: 300});
pre.show('loading');
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/joseluisq/prelodr/issues/33, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABnx4iNzAq-UhbDPOLWMiN_3kk5rkKuHks5rPM8QgaJpZM4LblH-
.

--
Saludos cordiales.
Best regards.
Viele Grüße.
José Luis Quintana | quintana.io

In the new v2.1.0 is deprecated. Please update your package.


[Automation] Automation mod crashes in the editor

A fix, suggested by @todoralin:
"Scenes": [
        "All",
]

The tool resources are loaded in any mode.

As a workaround, the editor was added to the scenes.


What is the point of attempting to parse the message as JSON?

All this does is create spurious exceptions. Why not just pass the message through and let the application deal with it?

The reason is to unify the data in a same format, so that notifications could be received from the Core PCL project when working with multiple platforms.

Will you suggest a better approach when having a cross platform application solution?

The json is actually fine as one cannot be certain what the content is at the moment or will be in the future, the dictionary in the past was fine as long as the notification was simple but taking full advantage of notication was a bit hard.
If one has issues than they should create a few platform specific handlers that work based on criteria and transform the required information to a model/struct that can be used in a shared environment or pass the information to the platform, of course don't forget one or two more global unhandled handlers to show a message or so for future actions/handlings.


Konosuba - Attack of the Destroyer [PCSG01093]

Game summary

Game name: Konosuba - Attack of the Destroyer
Game serial: PCSG01093

Vita3K summary

Version: 0.01
Build number: 404
Commit hash: https://github.com/vita3k/vita3k/commit/d4cd595

Test environment summary

Tested by: waterflame
OS: Windows 7
CPU: Intel i7-2600
GPU: AMD Radeon HD 6700 Series
RAM: 8 GB

Issues
Softlocks on sceFiosOverlayGetRecommendScheduler02.
Screenshots

Log
vita3k-404.log
Recommended labels

Softlock

Vita3K summary

Version: v0.1
Build number: 984
Commit hash: fb0798e of pull/456 (I don't want to append every issue to the PR)

このすば Attack of the Destroyer - [PCSG01093].log
Issue
stat fail error

Game summary

Game name: Konosuba: Attack of the destroyer
Game serial: PCSG01093
Game version: 1.01

Vita3K summary

Version: v0.1
Build number: 1076
Commit hash: https://github.com/vita3k/vita3k/commit/bc03af6

Test environment summary

Tested by: Zangetsu38
OS: Windows 10
CPU: AMD Ryzen 2700X
GPU: NVIDIA GTX 1080 Ti
RAM: 16 GB DDR4 3600 mhz

Issues

Mutex error

sceKernelSignalLwCondAll returned SCE_KERNEL_ERROR_LW_MUTEX_RECURSIVE (0x80028182)

Log
vita3k.log

Vita3K summary

Version: v0.1
Build number: 1315
Commit hash: https://github.com/vita3k/vita3k/commit/5b070aac

-errors on direcory reading(sceIoDopen/Dread/dclose) and file stating. Might also be the sceKernelChangeThreadVfpexception,sceFioOverlayThreadSetDisabled02, or sceFiosOverlayGetRecommendedScheduler02
KonosubaAOTD.log

Moved from https://github.com/Vita3K/compatibility/issues/458
App summary

App name: この素晴らしい世界に祝福を！ATTACK OF THE DESTROYER
App serial: PCSG01093
App version: 1.00

Vita3K summary

Version: v0.1
Build number: 1827
Commit hash: https://github.com/Vita3K/Vita3K/commit/0f2aabb900ddd27078df540bfe8f1d177ff0445d

Test environment summary

Tested by: Arnold Secret
OS: Windows 10
CPU: Intel Core i7-4500U
GPU: NVIDIA Geforce GT 740M
RAM: 8 GB

Issues
Reaches to MAGES logo, then crashes.
Screenshots

Log
vita3k.log

Moved from https://github.com/Vita3K/compatibility/issues/458
App summary

App name: この素晴らしい世界に祝福を！ATTACK OF THE DESTROYER
App serial: PCSG01093
App version: 1.00

Vita3K summary

Version: v0.1
Build number: 1827
Commit hash: https://github.com/Vita3K/Vita3K/commit/0f2aabb900ddd27078df540bfe8f1d177ff0445d

Test environment summary

Tested by: Arnold Secret
OS: Windows 10
CPU: Intel Core i7-4500U
GPU: NVIDIA Geforce GT 740M
RAM: 8 GB

Issues
Reaches to MAGES logo, then crashes.
Screenshots

Log
vita3k.log

App summary

App name: この素晴らしい世界に祝福を！ATTACK OF THE DESTROYER
App serial: PCSG01093
App version: 1.01

Vita3K summary

Version: v0.1.2
Build number: 2083
Commit hash: https://github.com/Vita3K/Vita3K/commit/dc460ddb83fd87385212e8732221bbbeab89b47f

Test environment summary

Tested by: SPdream
OS: Windows 10
CPU: Intel Core i5-4460
GPU: NVIDIA GeForce GTX 1060 3GB
RAM: 16 GB

Issues
It seems to be playable with just some graphic glitches.
Screenshots

Log
vita3k.log

Try with different loaded modules, if it still gives error then comment again with the modules you have loaded and upload logs, not only a screenshot

Try with different loaded modules, if it still gives error then comment again with the modules you have loaded and upload logs, not only a screenshot
which module do you recommend using and how to share the logs?

PCSG01093.zip
shaders log

which modules i cannot say, try automatic and if that doesn't go ingame then try manually, logs are stored inside the folder where Vita3K.exe is stored

Shaders logs shouldn't be shared, those are specific to your GPU and are somewhat game code so delete that comment, it can get into trouble

Could not find firmware font file at "C:/Users/Utilizador/AppData/Roaming/Vita3K/Vita3K/sa0/data/font/pvf\ltn0.pvf", install firmware fonts package to fix this.

What's that ?

vita3k.log

Konosuba Attack of the Destroyer
The Game is Playable
60 FPS
but when start the game it's freeze
Graphics Glitches

RETESTED
Vita3K summary

Version: v0.1.8
Build number: 3160
Commit hash: https://github.com/vita3k/vita3k/commit/[1c009661]
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: JackMonty
OS: Windows 10
CPU: AMD Ryzen 5 Pro 3500U
GPU: Nvidia Geforce GT1030
RAM: 32 GB

Issues
Game runs full speed, no crashing - there is graphical issues on the sides but this doesn't stop the game from being playable in my option.
Screenshots
Title Screen

Character Select:

Shop

Gameplay with Graphics Bug:

Gameplay should like this:

Log
vita3k.log
Recommended labels

Playable
Graphics Bug

This game needs Enable Optimizations to be disabled to get past MAGES logo.


C# Script Properties source generation fails for escaped reserved keyword exports

Tested versions

Reproducible in: v4.2.2.stable.mono.official [15073afe3]

System information
Godot v4.2.2.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 (NVIDIA; <IP_ADDRESS>23) - 12th Gen Intel(R) Core(TM) i9-12900 (24 Threads)
Issue description
Using reserved keywords escaped with @ for exported variable names in a C# Resource/Node class results in invalid generated source from Godot.SourceGenerators.ScriptPropertiesGenerator
Steps to reproduce

Create a C# partial class inheriting either Node or `Resource
Add an [Export] field using a reserved name (you can escape reserved names with the @ symbol, i.e. @operator, @class, @interface, etc.)
Build the project, and see the compilation errors (since the generated source code does not escape the reserved keywords, so the resultant code is invalid)

Example code:
namespace FailureReservedKeywords;

public sealed partial class MinimalRecreation : Resource
{
    [Export] private int @operator = 0;
}

Resultant compilation errors:
0>FailureReservedKeywords.MinimalRecreation_ScriptProperties.generated.cs(16,70): Error CS0106 : The modifier 'new' is not valid for this item
0>FailureReservedKeywords.MinimalRecreation_ScriptProperties.generated.cs(16,70): Error CS0106 : The modifier 'readonly' is not valid for this item
0>FailureReservedKeywords.MinimalRecreation_ScriptProperties.generated.cs(16,70): Error CS0501 : 'MinimalRecreation.PropertyName.operator +()' must declare a body because it is not marked abstract, extern, or partial

Minimal reproduction project (MRP)
N/A (see above example code, as this is enough to recreate the issue in any project). This error is C#-specific.

Duplicate of https://github.com/godotengine/godot/issues/74839


Try to fix upload-artifact@v4 issue

Many thanks for submitting your Pull Request :heart:!
This pull request aims to fix the issue #599.
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to our code style
[ ] Pull Request title contains the target branch if not targeting main: [0.9.x] Subject
[ ] Pull Request contains link to the issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-quarkus2 to backport the original PR to the quarkus2 branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@mcruzdev  I think the variable name is not getting from the matrix var. See:  Artifact site-{{ matrix.java.version }}-{{ matrix.os }}.zip successfully finalized. Artifact ID<PHONE_NUMBER>

Another improvement, I think we can build only once the website in the preview pipeline. Doesn't make much sense publishing 4 artifacts in each matrix run.

Another improvement, I think we can build only once the website in the preview pipeline. Doesn't make much sense publishing 4 artifacts in each matrix run.

$ sign mistake, TY.

Another improvement, I think we can build only once the website in the preview pipeline. Doesn't make much sense publishing 4 artifacts in each matrix run.

$ sign mistake, TY.

Thank you for fixing it!!

@ricardozanini WYT about creating just one job to generate the site documentation and consume it in preview.

@ricardozanini WYT about creating just one job to generate the site documentation and consume it in preview.

Yes, exactly. We should remove the website upload from the matrix build. The other CI can just build skipping test since it's only interested in the website generation.

Done @ricardozanini :)

Awesome! Thank you very much @mcruzdev ❤

@all-contributors add @mcruzdev for code and documentation.


Bugfix: lr scheduler kwargs handling

fixes #271
The **kwargs passed to LRScheduler used to be saved as kwargs
attribute but now vars are updated instead. This allows to clone
LRScheduler and to set_params on those kwargs.

This is a clever way to get around how sklearn does not like **kwargs in __init__ without changing LRScheduler's API.
LGTM


KML

Is there a way to display a KML in the current version of the application?  If not, I may start working on it and can contribute my changes, but before I did that, I wanted to see if it already existed somewhere in the code.
I am looking and I don't see it...
Thanks!

Hi,
No, the current version does not have that feature. Contributions are welcome.

Hi @pjsimon4321,
Just pushed a set of changes to allow displaying a Kml layer through GoogleMap control for Asp.Net MVC. To see the details please review this sample.
The changes are in dev branch. Please review them and let me know your thoughts.

Hi @jmelosegui,
This is fantastic ! I was starting looking for KML layer, I have 2 issues, when I build from the new source two build errors are found (mapobject.cs - line 13 and infowindow.cs - line 29), when "fixing" it I have then another error :
Unhandled exception at line 37, column 59140 in http://localhost:33868/0a0795d1180b4483bbadcda9aeed7056/browserLink
0x800a139e - JavaScript runtime error: Syntax error, unrecognized expression: unsupported pseudo: plusone
it still work but I keep getting the error every time I click on something (note that I run the test on http://localhost:24576).
Any help will be greatly appreciated !

Hi @jpgutton,
See following answer, that works for me.
http://stackoverflow.com/questions/20244048/javascript-errors-when-debugging-in-visual-studio-2013?answertab=oldest#answer-22213274


Generated client does not honor @http trait

Hello,
We define our HTTP endpoints using the @http trait on operations, e.g.:
@http(uri: "/create_account", method: "POST")
operation CreateAccount {
...

Taken from https://awslabs.github.io/smithy/1.0/spec/core/http-traits.html
But these paths are nowhere to be found in the generated go client.

This issue is similar to https://github.com/aws/smithy-go/issues/354. Since the smithy-go codegen does not include any protocols implementation it cannot understand the @http trait. Lets use #354 to track this general concept and feature request.


Revert "feat: Reset password after confirming email-link and 'Forgot password, send me a reset-link' possibility"

Reverts runoutnow/Flask-AppBuilder#2

Codecov Report

Merging #3 (dbbcd16) into master (af7e0c1) will decrease coverage by 30.89%.
The diff coverage is 15.50%.

@@             Coverage Diff             @@
##           master       #3       +/-   ##
===========================================
- Coverage   73.07%   42.18%   -30.90%
===========================================
  Files          46       46
  Lines        6463     6477       +14
===========================================
- Hits         4723     2732     -1991
- Misses       1740     3745     +2005

Flag
Coverage Δ

python
42.18% <15.50%> (-30.90%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

flask_appbuilder/security/sqla/manager.py
0.00% <0.00%> (-66.16%)
:arrow_down:

flask_appbuilder/security/manager.py
36.17% <8.94%> (-23.33%)
:arrow_down:

flask_appbuilder/api/manager.py
55.10% <20.00%> (-42.52%)
:arrow_down:

flask_appbuilder/api/convert.py
20.14% <27.27%> (-71.40%)
:arrow_down:

flask_appbuilder/api/__init__.py
40.74% <66.66%> (-56.86%)
:arrow_down:

flask_appbuilder/security/mongoengine/manager.py
60.34% <100.00%> (ø)

flask_appbuilder/security/sqla/models.py
0.00% <0.00%> (-97.94%)
:arrow_down:

flask_appbuilder/models/generic/interface.py
0.00% <0.00%> (-92.31%)
:arrow_down:

flask_appbuilder/models/generic/filters.py
0.00% <0.00%> (-78.38%)
:arrow_down:

... and 29 more

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 6bc4047...dbbcd16. Read the comment docs.


[BUG] Code generation script is not working after cognitive service folder structure is changed

Describe the bug
According to the documentation, we should run the generate.ps1 powershell script to generate SDK code. However, due to a recent change to update cognitive services folder structure, the script doesn't work any more.
Exception or Stack Trace
Add the exception log and stack trace if available
> E:\Source\cognition\azure-sdk-for-net\sdk\cognitiveservices\Vision.ComputerVision\src\generate.ps1
Start-AutoRestCodeGeneration : Could not find root for output directory since script is not run from SDK repo, please provide this using the -SdkRepoPath parameter!
At E:\Source\cognition\azure-sdk-for-net\sdk\cognitiveservices\Vision.ComputerVision\src\generate.ps1:1 char:1
+ Start-AutoRestCodeGeneration -ResourceProvider "cognitiveservices/dat ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Start-AutoRestCodeGeneration

To Reproduce
Run generate.ps1 under sdk\cognitiveservices\Vision.ComputerVision\src.
Code Snippet
Add the code snippet that causes the issue.
Expected behavior
SDK code should be generated under the script folder.
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):

OS: Win10

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

Not sure if this is Client or Management plane.  @AlexGhiondea and @shahabhijeet, would you guys take a look and label appropriately?

I think it's Client plane.

@kurtzeborn it looks like the folder structure broke some of the scripts in this repo.

@chidozieononiwu can you take a look at this.

We should hand this one off to the management plane folks.

@kurtzeborn @chidozieononiwu  We are hitting the same issue in Event Grid. Is there a workaround or known mitigation steps?


Cookbook example bridging QueryBatcher to Data Services.

So we can incorporate your pull request, please share the following:

What issue are you addressing with this pull request? https://project.marklogic.com/jira/browse/JAVA-166
Are you modifying the correct branch? Yes, develop
Have you run unit tests? Yes
Version of MarkLogic Java Client API - 5.1.0
Version of MarkLogic Server (see admin gui on port 8001)
Java version (java -version)
OS and version
What Changed: What happened before this change? What happens without this change?

Included both the changes.


Repeated suggestions

VS Code Version: 1.29.1
VS Code Inellicode Version: 1.1.0
OS Version [macOS/Windows]: Windows 10
Target Platform or Language [e.g. Python]: TypeScript 3.1.4
Seeing many of the same suggestion:

They're all repeated exactly 10 times, except stack, which has 9 "stack"s and a "stack?":

Not sure how to specifically repro. Just installed the extension and this is the first suggestion I've gotten. Very large code base.
Type type in question is the TypeScript Error interface:

Hope that helps! Thanks for including TypeScript. Really excited about Intellicode, and happy to have the preview.

Thanks for the report. Do you have a lot of tsconfig.jsons in your project, by any chance? I wonder if the IntelliCode plugin is getting loaded separately for each project.

Yes. There dozens of tsconfig.json files. I'v sent you a message on Teams, if you want to see anything specific.

I'm still trying to hit a repro with your project but haven't been able to. Please feel free to send me logs if ever you hit it again.


Add docker-compose file to provide a Redis instance for this course.

Add adocker-compose.yml file that uses the Redis Docker container (https://hub.docker.com/_/redis), and configure Redis in that container to persist data to a folder named "redisdata".
This is part of our participation in Hacktoberfest 2021.  Learn how to complete this issue here: https://developer.redis.com/hacktoberfest/
Need help or want to talk to us?  Join us on Discord where we have a dedicated Hacktoberfest channel: https://discord.gg/ueQwKUh5Z3

@NarayanAdithya yes, that's right so something similar to this (this one uses the redismod container but for this course here we don't need modules so you can use the redis container that doesn't have modules) https://github.com/redis-developer/redis-kaboom-rpg/blob/main/docker-compose.yml
I've assigned this to you, check out our guide at https://developer.redis.com/hacktoberfest/ and have fun!


Deploy RGW as part of Ceph deployment

It's possible to configure Swift with an external RGW backend. This change allows the Ceph deployment to support a configured external RGW instance that can serve swift related requests.
The main ceph playbook has been modified to include the rgw task, and a spec template is rendered to deploy both RGW and the related Ingress daemon via ceph orchestrator.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:
[x] README in the role
[x] Content of the docs/source is reflecting the changes

recheck

We usually use fully qualified names for ansible module calls. Please update to match it - even for builtin modules :).

ack I think it's done (Note I did it for the portion of code relate to this patch): for all the other occurrences I'll follow up on a different patch.


Default template for monolingual and bilingual dictionary

A default template that can be chosen when a user starts a new dictionary. You can already choose from default templates in Lexonomy, but these need to be adapted to the DMLEX model (See: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=lexidma).

We need someone to create the templates, ideally containing several entries of different type (various PoS, etc.)
connected with #21


Returns Block in android even if the permission is granted in the settings

I want to send the user to the settings if he block the permission so he will activate the permission from there. it works great on IOS, but in android, after I blocked the permission and granted the permission in the settings if I check the permission, I get "blocked" instead of "granted".
What should I do?

@eldareini Please fill the issue template, please. I'm not supposed to guess what's your environment.

@zoontek
sorry, you are right
System:
OS: macOS 10.15.4
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Memory: 571.56 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 13.11.0 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.13.7 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
IDEs:
Android Studio: 3.6 AI-192.7<IP_ADDRESS>41897
Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: ^0.61.5 => 0.61.5
npmGlobalPackages:
react-native-cli: 2.0.1
Library version: 2.1.0

@eldareini Thanks. I published a fix, as version 2.1.2
Please update and check if it solves your issue 🙂

@zoontek Thanks, that fixes the issue 🙂


when a media item is replaced, hide the old version in uploadfs. Crea…

…te an array of uploadfs paths to the old versions and be sure to remove them in apostrophe:empty-trash

Traced through the logic here, looks good to me. It appears hideInUploadfs should behave the same way as it did before for trashing a file, which is correct. Merging.


Survey biomass estimates

Survey estimate does not match between Table 13 and Table 14 for 1998.
In the code it looks like survey.history and survey.summary are used, and survey.summary has biomass.2016 and biomass.2017 where the values are different for 1998 between the two columns.
What do we do?

Also, after we fix this, Table 14 is entirely contained in Table 13. Do we remove the latter?

Let me double check but I believe there was an update to that survey data point in between those years, so we should be using the most recent estimate of 1998.

The 2017 assessment updated the 1998 survey biomass estimate.  The bridging section from that assessment says "Updates included Pacific Hake assessment 2017 45 Section 3 – Assessment
a revised estimate and standard error for 1998, a revised standard error for 2015 estimate, and
the extension of the survey time series to include 1995"
Also says: "As part of that data-processing step, it was discovered that the variogram used in the kriging for the 1998 data required a revision, which resulted in a increase in the biomass index for that year
of approximately 2%, from 1.534 to 1.569 million t, and a decrease in the associated CV from
0.0526 to 0.0479. The coefficient of variation estimated for the 2015 survey was revised in early
2016 from 0.092 to 0.0829."
So it looks like Table 14 is correct and the 1998 values in table 13 (biomass index and sampling CV) need to be updated.
And yes, we could get rid of one but let's not for now as we are so close to deadline.

Okay I will fix the table code to make Table 13 match Table 14.

I'm sure you know but those data are in csv files in the data folder

Sweet, easy fix. I won't even open it in excel :)

I think we are good here, right?

Yep all fixed for 2019. Could add to 2020 with a note to truncate to the larger table.

So ... I was trying to accommodate Trevor's request for "Figure 9 should be deleted since the same information is contained in Figure 10 (other than the squid adjustment)" and discovered that our data file is using the wrong survey estimate for 1998 and did so in the 2018 assessment as well. The 2018 and 2019 base-model files use a value of 1534604 and se of 0.0526 where in 2017 the 1998 survey was 1569148 and se of 0.0479.
I started a new mcmc run at around 5 am based on 2019.03.00_base_forecast4 that I call 2019.03.60_fix1998survey, where the only difference in the MLE files is the 1998 survey and se and then for the MCMC I also fixed the second DM parameter at its MLE value specific to this run.

Good catch Kelli, I don't know how that got changed in 2017 and then reverted in 2018 and kept in 2019.  The latter seems quite possible, but the former seems odd.  Because 2018 was a survey year, perhaps the survey file we got from the survey team didn't have that change in it (?) and we just inserted the new survey data.
In the 2017 assessment when we originally updated the 1998 survey value, the bridging model showed essentially no difference throughout the time series.  We can show (or just discuss) that result again this year with an MLE model at the SRG (2019.03.00_base compared to 2019.03.60_fix1998survey).  I don't think we need to put anything in the final assessment other than a sentence or two about this value being corrected again for the 2020 assessment.  We should 2020 milestone this issue so we don't forget to triple check this number next year.
Kelli, can you put a model folder on the drive that includes the MLE run for 2019.03.60_fix1998survey while you wait for the MCMC to finish.  And actually, for comparability to our base.model, shouldn't we set off an MCMC based on 2019.03.00_base (not forecast4) - due to the extra parameter in forecast4 the MCMC start value doesn't match our base.model because the counter gets off with different number of parameters.  The resulting posterior of the median estimates between _base and _base_forecast4 are rather close (as expected) but not the same.  And the MCMC results from this run can be used to just confirm this change makes no difference for current management and thus doesn't warrant redoing/updating the whole assessment this year.

The model is on the drive. You might want to compare the report files because there are some changes. I am not entirely sure what is justified as being for concern though.

Should I stop this mcmc and change the comparison to the base, I think it wouldn't matter if we compare to the four year or three year model and I did the four year so that the comparison could include the end of the year forecast as Trevor suggested.
I guess this points to a larger question for me, in the future are we going to keep this 4-year forecast or go back to the 3-year forecast?

My thought is no, we will not move to 4-year forecasts.  'We' (Ian mostly) has been fairly consistent with the JTCs response to (in particular) the JMC when in the past they have asked for longer forecasts.  I agree with his response that given sigmaR and estimated interannual recruitment variability forecasting out 3 years is already pushing it (at least in terms of forecasting for use in current TAC management decisions). I view this as different than 'on average' decisions that come from longer MSE-style simulations.  So... my vote would be to stick with 3-year forecasts and for the beginning of the year spawning biomass decision table just remove the catch values for 2021; they can stay in there for relative fishing intensity table though because that's still okay.

Ahh okay, sorry I didn't follow that thread very well. I will switch the comparison to the true base model then.

It would be good to have a collective JTC opinion on this for the SRG meeting next week.  We can discuss in person on Monday evening too.  Kelli, maybe just leave your current MCMC run going.  We can compare that to the other forecast4 one.  I've attached an SSplotComparison set of plots between the two models to show no difference.  Again, I'm not sure its worth even discussing this other than during the data presentation just saying this happened and it makes essentially no difference - if they want to see it themselves we can show.
Compare_SelectSensModels.pdf

Too late, I already stopped it :)

Your too fast!
And of course we can say that we have 'earmarked' this issue to ensure it will be resolved moving forward....

Seem reasonable?  Phew, that issue was not expected first thing the Saturday before the SRG meeting... adrenaline started to kick in and got an 'oh shit' feeling for a short while.  I'm so glad you caught it though Kelli b/c this could have lingered for years...

Okay, we are back in business, mcmc is running to compare to the real base with 3-year forecast. I am also almost done with commits that remove the second survey table and the first survey figure (i.e., Table 14 and Figure 9). I am unsure if we should just leave the figures in there until the SRG meeting is done that way when people are referencing figure numbers they will be the same as the PreSRG document and we don't get confused.

Totally agree to not change our pre-SRG document.  This is an improvement
so we can make this change to our final document.  So okay to commit, just
be sure to use the pre-SRG version during the meeting when referencing
things.  We should all have the same document (except I think Chris has
different page numbers), but just in case our pre-SRG draft that was sent
out is on the google drive under document.
On Sat, Feb 16, 2019 at 8:51 AM Kelli Johnson<EMAIL_ADDRESS>wrote:

Okay, we are back in business, mcmc is running to compare to the real base
with 3-year forecast. I am also almost done with commits that remove the
second survey table and the first survey figure (i.e., Table 14 and Figure
9). I am unsure if we should just leave the figures in there until the SRG
meeting is done that way when people are referencing figure numbers they
will be the same as the PreSRG document and we don't get confused.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/cgrandin/hake-assessment/issues/539#issuecomment-464362216,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHk_-iNPnVgSAotCdNSwG0mVitMuhk7vks5vODchgaJpZM4amMfW
.

--
Aaron M. Berger, Ph.D. Research Mathematical Statistician
Fishery Resource Analysis and Monitoring Division
Northwest Fisheries Science Center
2032 SE OSU Dr. Bldg. 955
Newport, OR 97365-5275
<EMAIL_ADDRESS><EMAIL_ADDRESS>

I guess this is a good a place as any to bring this up, but why are models being run with forecasts being anything other than 1 year? All out models should have forecasts set to 1 year since we run the forecasts later from R code. Having extra unused years in the base part of the models is confusing.
We can run forecasting on the base model out to 4 years and re-generate the decision table that Trevor wanted to see based on that instead of the forecast4 mcmc run (which has an extra pointless parameter).
I realize you are running new MCMCs for survey point changes but I wanted to mention this.

Thanks Chris. I think that we should talk about this on Monday so that we can have a plan moving forward regarding forecasts. I don't fully understand how they are done yet, so I will put looking into it better on my todo list.
The commit to fix the table and plots regarding the survey index is here. Let me know if you don't like the new plot that integrates the two. See below.

Still need to do the following:

[ ] Add something to the data slide
[ ] Add a line of text to the assessment?


Please add back renaming Hourglass9.bin

Minor issue, but a couple of people were freaking out about the CTRNAND error message because they couldn't boot into Hourglass9

Seems like everyone who has the “Failed to mount CTRNAND” error cant start houglass9 through luma3ds cl menu. The part with manually renaming and booting directly into hg9 fixes this for those people. There are constantly people coming to Q&A on discord having this problem.


Q about premature/advanced

Is premature really the same as advanced? To me premature implies that something occurs before something else in a sequence (when it should occur after), whereas advanced implies quicker than normal (may be because it has jumped ahead in a sequence, or because things ahead in the sequence completed faster than normal)
ID 	FYPO:0000479
Ontology 	fission_yeast_phenotype
Term name 	premature meiosis
Definition 	A cellular process phenotype in which one or both meiotic nuclear division(s) occurs prematurely.
Synonyms
advanced meiosis
meiosis: premature
premature meiotic nuclear division

Is premature really the same as advanced?

According to PATO, yes (although "advanced" also has some slightly different possible meanings in vernacular English, for phenotype definitions we ignore them, and follow PATO).
I see that I haven't been totally consistent in whether "premature" or "advanced" is in the term names, nor in making sure the definitions include "begins earlier than normal". I'll tidy those up.

[Term]
id: PATO:0000694
name: premature
alt_id: PATO:0000691
alt_id: PATO:0002086
def: "A quality of a process which starts earlier than the natural start time or the reference process." [PATO:LC]
subset: value_slim
synonym: "advanced" EXACT []
synonym: "early" RELATED []
synonym: "precocious" RELATED []
is_a: PATO:0002325 ! onset quality

ok cheers!

all tidied - standardized on 'premature' in names and 'advanced' in exact synonyms, and made sure def wording is consistent

edit file: fedad3dc05dbea79bf554eff4835023ad8a5ab61
release: 154d4089fe3156b9a93a5cd829b2c555ac49371b


Check all screens so that they match the design

We need to check all screens in the wallet so that they match the design.

Checked.


[bug] 1.0.1-beta.194 compiler is broken with the use of react-native-svg or @tamagui/lucide-icons

Describe the bug
As soon react-native-svg is in use (or @tamagui/lucide-icons) of my/ui NextJS is not compiling.
To Reproduce
Clone https://github.com/dohomi/tamagui-194-bug which is a reproduction of this bug. It essentially only adds one icon into MyComponent which breaks NextJS from compiling
The reproduce is the tamagui starter with only one line added to the component:
https://github.com/dohomi/tamagui-194-bug/blob/main/packages/ui/src/MyComponent.tsx#L12

Fixed in two ways: https://github.com/tamagui/tamagui/commit/0040389044bbf1734010de62c2e9ac141d10a85d https://github.com/tamagui/tamagui/commit/b8c500ffc57dc46c53c612adb30c9823661e0b00


Add support for swift snapshot swift-DEVELOPMENT-SNAPSHOT-2016-05-03

The following fork compiles with swift-DEVELOPMENT-SNAPSHOT-2016-05-03: https://github.com/necolt/Stencil

The mentioned fork compiles with swift-DEVELOPMENT-SNAPSHOT-2016-05-09 without warnings.

Swift 3.0 support has been added in Stencil 0.6.0.


Failed by using React Component

Hi Flowbite Team,
I followed you tutorial to install Flowbite https://flowbite.com/docs/getting-started/react/.
By importing any Component into my React App e.g. import { Button } from 'flowbite-react';, I receive the following error:
Failed to compile.

./node_modules/flowbite-react/lib/esm/components/FormControls/HelperText.js 17:21
Module parse failed: Unexpected token (17:21)
You may need an appropriate loader to handle this file type.
|     className: classNames(theme.base, theme.colors[color], className)
|   }, props, {
>     children: value ?? children ?? ''
|   }));
| };

Could you please help to resolve such issue? Thank you very much!

Check this:
https://github.com/themesberg/flowbite-react/discussions/169


Some JAR files will be empty

Expected behavior
No warnings during build
Actual behavior
[INFO] --- maven-jar-plugin:3.0.0:test-jar (default) @ pulsar ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /Users/masakazu/git/pulsar/target/pulsar-tests.jar

[INFO] --- maven-jar-plugin:3.0.0:test-jar (default) @ distribution ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /Users/masakazu/git/pulsar/all/target/distribution-tests.jar

Steps to reproduce
mvn install -DskipTests

System configuration
Pulsar version: master c51eaad
OS: macOS 10.12

#678 fixes this.

Merged #678


all: use byte array backing for result and variant data

This PR implements a change to how result and variant types are represented in Go, namely generating a storage shape sized to match the largest associated type.

It implements an experiment, enabled by default, to generate byte array backing for result and variant data fields. This makes the ergonomics of using generated code slightly worse, by introducing single-use types, e.g. Shape1 into caller-visible code.
It implemented, then reverted, a fix for the data shape of result and variant types using arrays. This fix, does not work with TinyGo (LLVM), so it was abandoned (see e9d6c260fc6167ba32ee546295f14b91d0fe2982).

This corrects an issue with the original implementation, which used a Go type parameter Shape in Variant and *Result types. If a variant shape was a struct with "holes," e.g. a uint8 followed by a wider type, say uint32, then the 3 bytes between the fields may not be passed to the caller if the variant or result type is passed on the stack.
Fixes #95.

@rajatjindal try again, I updated how it works.

Hi @ydnar, this still works as expected 👍 (with my limited testcases that I've been trying). thank you

Hi Randy,
I am still trying out these changes, and have an additional request:
could we please make the name of the shape struct predictable?
e.g.
for type ErrorCode struct, can we make it type ErrorCodeShape struct.
The problem I am anticipating we might run into is when we change the WIT file, the generated code might be different and have different names of these shapes, which will force changes in SDK's built on top of generated bindings.

I’ve reverted the change to use deterministic shape type names. Thanks for the feedback!

@rajatjindal one last shot, can you try this?

sure thing, I just tried and the tests on my side worked 👍


[WIP] Tsdb gw refactor

This is a starting point for the Refactor into two separate binaries.
Interested in suggestions on how publishing can work with both cortex and metrictank.
I'll comment specific lines of code with particulars

Replacing the worldping logs is gonna require handpicking through the current log lines and reformatting them, since some are gonna look weird due to function changes

@Dieterbe @tomwilkie @woodsaj @replay I think this is ready for another look.


Enable rpm/deb testing of non-x64 Linux packages

At the moment we do not have the support for running TestContainers on non-x64 platforms. We should look at implementing something that allows us to run the installer testing on the other architectures which we support.

The year ago now that we talked with the TestContainers folks, there was a way to add support for non-x64 platforms.  Need to find the notes from that, something about changing Ryuk, but also its a year ago, and seems there are official updates that may help us: https://twitter.com/whichrich/status/1341730726270492672.

Yep, whether it's with "official" options (0bviously preferred if we can) or just something we knock up ourselves to do a basic install and java -version we should get something in place. Obviously not necessary for this first release as we can verify manually but has to be "on the list".

Once this gets enabled, those hard-coded values need to go: https://github.com/adoptium/installer/pull/379/files#diff-fdcc04743d05ab4da45b68037fc038027fbc92cb032e305ebc832642db38875aL37-L38
E.g. via an environment variable ARCH or some such.

related: https://github.com/testcontainers/moby-ryuk/pull/21

Just a note:
1 . newly enabled sle12 may not be enable to add tests? https://github.com/adoptium/installer/pull/426/files
2. probably will be enabled in a short time RHEL6 https://github.com/adoptium/installer/pull/412/files

For those watching, linuxNew has been renamed to linux

It shouldn't be using dockerBuild as that's exclusively for hosts configured to run the dynamically generated docker images we use for building the JDK. docker should be a suitable one to use instead:
https://ci.adoptopenjdk.net/label/docker&&linux&&(s390x||armv7l)/