Deprecated tag 'alt_name_1' is still proposed by ID

How to reproduce the issue?

Select an object (eg a track)
in its attributes, start typing 'alt' in a new attribute
observe that a list of possible values appears, among them 'alt_name' and 'alt_name_1'.

Remark: if the 'alt_name' key is already in use for this object, the default value of the list proposed by ID is the deprecated tag 'alt_name_1'.
Screenshot

Which deployed environments do you see the issue in?
Released version at openstreetmap.org/edit
What version numbers does this issue effect?
2.23.2
Which browsers are you seeing this problem on?
Firefox

Or, someone could create a MapRoulette Challenge to get rid of this data from OSM for good. It's "only" 12k … https://taginfo.openstreetmap.org/search?q=alt_name_1
The idea of the raw "Tags" view ist to be a sharp knife for those that know what they are doing.
What percentage of new alt_name_1 tags are added by iD (in recent years)?

@bryceco

439 of those alt_name_1 instances are this highway. What is the correct replacement in this case?

History: I remember reading somewhere (I think in this repo) that most of those _1 keys are from a time when imports where made (TIGER?) and from years ago when iD (silently?) appended _1 to keys whenever a duplication happened in iD. A practice that AFAIk has long been abandoned.
About the replacement: That is a good question for the OSM forum / tagging mailing list / a proposal page IMO. My take would be: We have two concepts to represent "this key has mutliple values".
Appending :1, :2 to tags. I personally never liked this, but the old and recently deprecated parking:lane schema documented it as valid solution. From the top of my head I don't know if any other schemas use this. However, it would be more in line with how "subkeys" are build (like source:maxspeed) than the underscore solution.
A better solution IMO would be to follow the semicolon pattern for key that have multiple values. That's at least well established. And for this particular case of alt_name=Interstate Highway 10 West; IH-10 West; Interstate 10 West, IMO a better solution the those _1s. Data consumers like Nominatim could do a full test search on the semicolon field and still produce valid results.

I remember reading somewhere (I think in this repo) that most of those _1 keys are from a time when imports where made (TIGER?) and from years ago when iD (silently?) appended _1 to keys whenever a duplication happened in iD. A practice that AFAIk has long been abandoned.

Yes, this is more or less how it played out. At the time of the TIGER import, tagging standards were still fluid enough that it wasn’t absolutely certainly wrong to add these suffixes, but the community definitely soured on them in the years that followed.
By the time iD added this functionality to the raw tag editor, the suffixes were already extremely common due to the TIGER import. iD’s behavior was more relevant for non-name tags; if not for this behavior, it would’ve still autocompleted name_1 etc. based on taginfo statistics. In any case, the suffixing was removed in 640730d38b55a22549465aada141475897619433.
Most number-suffixed tags that remain need manual review anyhow. For one thing, the TIGER name abbreviation expansion bot only touched name as far as I know, not the suffixed variants.


Close padding buffers if we quit current buffer

Close all padding buffers when we close current buffer at once, if we don't use VimRoomToggle to close VimRoom before. Please see diff and you can omit all commits except fc01956 :)

aha, I wanna this feature too, tried some hacks but your way seems better.

Thanks :)
On Mon, Oct 10, 2011 at 1:57 PM, georgexsh <
<EMAIL_ADDRESS>
aha, I wanna this feature too, tried some hacks but your way seems better.
--
Reply to this email directly or view it on GitHub:
https://github.com/mikewest/vimroom/pull/12#issuecomment-2343203

--
Don't Panic. 不要惊慌。

Ok. That's a lot of commits. :)
The feature sounds interesting. I'll take a look at fc01956 sometime this afternoon... Thanks for putting it together!

You are welcome. I like VimRoom very much :)

f9bbbc5 is not an elegant way to handle the edge case, but I can't come up with other ideas :(


after kubernetes upgrade, all mongodb databases are gone

Greetings,
continuation from this problem https://github.com/GoogleCloudPlatform/kubernetes/issues/12134
thanks brendan, after the update, nodes were restarted and all containers started without problems, but there is one thing I am really afraid of my mongodb instances.
I'm using this yaml file, just cut the container list.
apiVersion: v1
kind: ReplicationController
metadata:
  name: mongodb-shard1-controller
spec:
  replicas: 2
  selector:
    name: mongodb-shard1-controller
    version: v0
  template:
    metadata:
      labels:
        name: mongodb-shard1-controller
        version: v0
    spec:
      containers:
      - name: mongodb-node1
        image: gcr.io/app/mongodb3.0.4
        ports:
        - containerPort: 27017
          hostPort: 27031
        env:
          - name: REPL_SET
            value: kube_shard1
        volumeMounts:
          - mountPath: /data/db
            name: db-path
      volumes:
        - name: db-path
          source:
            emptyDir: {}

it may not be the best, but I am using it in production. after the nodes restarted, all replica sets of mongodb instances, could not connect on to each other, and other than that, databases are gone. and I could not get it back up w/databases. i don't know where is /data/db gone?
I'm using GCP, what is the best practice for database storages?

Could you share how to deploy a replica set mongodb? Thanks

@davidopp potential data loss -- can you please triage further?

@Icedroid image is private, you can build one of yours, and customise it to your needs. from the above yaml, duplicate the containers to any numbers you want, then supply it an rs.conf() you might want to pass it an env: HOST for node communications, just make sure it can communicate w/other nodes. and thats it

@Hokutosei It looks like you are using emptyDir for your database storage. This uses a directory on the local file system which isn't guaranteed to persist across pod restarts. And in particular, node upgrades currently delete the node and give you a new node (at least on GKE/GCE) so this will definitely destroy any data that you have written to the local disk. You should consider using a network backed volume (GCE PD, NFS, etc) for your database or making a snapshot / backup just prior to upgrading your nodes and then doing a restore after the nodes have been upgraded.
It's possible that with the right combination of replication and rolling update tuning you could avoid needing to backup and restore, because theoretically if you update nodes slowly enough, new nodes will get data replicated from the existing nodes prior to the existing nodes being upgraded. But this is very timing dependent (and the timing will change as your database grows) so I wouldn't count on it for production.

@roberthbailey thanks for the help, I understand it now.. will try to migrate to using GCEPD instead. just for the record, maybe we should update the docs from here that when an update occurs, nodes will be deleted w/storages etc.. I thought it was only during a kubectl delete pod mongodb-shard1

The GKE upgrade documentation makes it much clearer.
Under Important Considerations: "Any data in hostDir or emptyDir storage in pods is deleted during an upgrade/downgrade."
It looks like the Kubernetes documentation should be a bit clearer on what to expect during the upgrade process (although that is difficult because it varies based on the cloud provider).

Greetings,
that looks much more clearer! thanks @roberthbailey  I was looking at kubernetes storages, but then, i just lost around 300k records...
this looks resolved to me, please close this thread?

I want to create a mongodb replica set, But I don't how to init it  with three pods when the rc created.

@Icedroid currently, the RC's pod template can use PersistentVolumeClaims but all replicas would share the same claim (good for ReadWriteMany apps and providers like NFS).  But that's a limitation for scaling something like mongo where each pod requires its own volume.
You would have to create N claims in advance and create an RC for each claim and use Replicas=1.   This manual process is clunky and we're starting R&D to figure out a better scaling solution.

@markturansky Now I created a RC with Replicas=3,  I use kubectl describe pods/mongodb-xxxx get three pods IP. Then I exec into one of the pods to get into mongodb shell for running rs.initiate(conf) to init a mongodb replica set. Now I want to fine a method to do these automanually.

I'm going to close this since original issue is resolved.
@Icedroid please re-post your question to stackoverflow. We are trying to consolidate the channels to which questions for help/support are posted so that we can improve our efficiency in responding to your requests, and to make it easier for you to find answers to frequently asked questions and how to address common use cases.
Thanks for using Kubernetes.
The Kubernetes Team


Add more info to autoupgrade process

Questions
Answers

Description?
Add more info to autoupgrade process to better see what is going on.

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?

Sponsor company

How to test?
I think it's not needed to test it.

All good, all good but cs-fixer again :P


WIP: updated binding smtp doc: added AWS SES

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[ ] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
New binding AWS SES
Issue reference
https://github.com/dapr/docs/issues/1667

Waiting on https://github.com/dapr/components-contrib/issues/1019

This PR should target the pre-release branch which is now v1.4. Thanks


Update version of TanStack table library

Hello everyone!
I have been spending a lot of time trying to figure out why the data that I pass as props to the DataTable component is not being reactive?
Using Vue Dev Tools, I deleted data from the store, but the table was not updating or rerendering.
The problem is older version of the TanStack table in your components shadcn-vue/apps/www/package.json:
"tanstack-table": "^8.19.3"

There are also the same issues:

Reactive props for useVueTable
[Vue] Pushing to data ref does not add table row
docs: make  reactive

Support for reactivity in the Vue adapter was added on August 8, 2024 with the release of version:
"@tanstack/vue-table": "^8.20.0"

Latest version is v8.20.2
Please, update your library's package file to v8.20.0+

Hello, upgraded to "@tanstack/vue-table": "^8.20.2" on my project but still missing reactivity in the DataTable, any updates on this from your side ?

tanstack/vue-table version : "@tanstack/vue-table": "^8.20.2"
(didn't test with previous version)
Ok, I found a workaround :

Just go to the DataTable.vue
Add const data = computed(() => props.data) (below props for example)
Replace get data() { return props.data } by data in const table = useVueTable(...)

Full working example :
<script setup lang="ts" generic="TData, TValue">
import type { ColumnDef, ColumnFiltersState, SortingState, VisibilityState } from '@tanstack/vue-table'
import { FlexRender, getCoreRowModel, useVueTable, getPaginationRowModel } from '@tanstack/vue-table'
import { Table, TableBody, TableCell, TableHead, TableHeader, TableRow } from '@/components/ui/table'
import { valueUpdater } from '@/lib/utils';
import { computed, ref, watch } from 'vue';

const props = defineProps<{
    columns: ColumnDef<TData, TValue>[]
    data: TData[]
}>()
const emit = defineEmits<{
    (e: 'update:selected', value: {}): void;
}>();

const data = computed(() => props.data);

const sorting = ref<SortingState>([])
const columnFilters = ref<ColumnFiltersState>([])
const columnVisibility = ref<VisibilityState>({})
const rowSelection = ref({})

const table = useVueTable({
    data,
    get columns() { return props.columns },
    getCoreRowModel: getCoreRowModel(),
    getPaginationRowModel: getPaginationRowModel(),
    onRowSelectionChange: updaterOrValue => valueUpdater(updaterOrValue, rowSelection),
    state: {
        get sorting() { return sorting.value },
        get columnFilters() { return columnFilters.value },
        get columnVisibility() { return columnVisibility.value },
        get rowSelection() { return rowSelection.value },
    },
})

watch(rowSelection, (newValue) => {
    console.log(newValue);
    emit('update:selected', newValue);
});
</script>

The data should now be reactive again 🎉
Maybe it's a little "crappy" but that's the only way I found until now

Hello, upgraded to "@tanstack/vue-table": "^8.20.2" on my project but still missing reactivity in the DataTable, any updates on this from your side ?

Hi mate!
I am a backender and my knowledge in the frontend is weak, so could you tell me how to update the library correctly?
Should the component in shadcn-vue also use this new version when updating the library?
Also, for the sake of interest, how did you find this issue - through a Google search?
You can also see a new comment from contributors about this issue

@R0tmayer
You can use
npm add @tanstack/vue-table@latest

in your Terminal, in your project directory
Close this issue if you solve the problem
Thanks

I have a similar issue. If I use the examples from Tanstack to render the data using plain table it works fine. but if I use Shadcn table components then the reactivity is lost. I don't see the reason why, any ideas?
reproduced my issue: https://stackblitz.com/edit/github-pkcxux

tanstack/vue-table version : "@tanstack/vue-table": "^8.20.2" (didn't test with previous version)
Ok, I found a workaround :

Just go to the DataTable.vue
Add const data = computed(() => props.data) (below props for example)
Replace get data() { return props.data } by data in const table = useVueTable(...)

Full working example :
<script setup lang="ts" generic="TData, TValue">
import type { ColumnDef, ColumnFiltersState, SortingState, VisibilityState } from '@tanstack/vue-table'
import { FlexRender, getCoreRowModel, useVueTable, getPaginationRowModel } from '@tanstack/vue-table'
import { Table, TableBody, TableCell, TableHead, TableHeader, TableRow } from '@/components/ui/table'
import { valueUpdater } from '@/lib/utils';
import { computed, ref, watch } from 'vue';

const props = defineProps<{
    columns: ColumnDef<TData, TValue>[]
    data: TData[]
}>()
const emit = defineEmits<{
    (e: 'update:selected', value: {}): void;
}>();

const data = computed(() => props.data);

const sorting = ref<SortingState>([])
const columnFilters = ref<ColumnFiltersState>([])
const columnVisibility = ref<VisibilityState>({})
const rowSelection = ref({})

const table = useVueTable({
    data,
    get columns() { return props.columns },
    getCoreRowModel: getCoreRowModel(),
    getPaginationRowModel: getPaginationRowModel(),
    onRowSelectionChange: updaterOrValue => valueUpdater(updaterOrValue, rowSelection),
    state: {
        get sorting() { return sorting.value },
        get columnFilters() { return columnFilters.value },
        get columnVisibility() { return columnVisibility.value },
        get rowSelection() { return rowSelection.value },
    },
})

watch(rowSelection, (newValue) => {
    console.log(newValue);
    emit('update:selected', newValue);
});
</script>

The data should now be reactive again 🎉
Maybe it's a little "crappy" but that's the only way I found until now

Updated to latest version using npm add @tanstack/vue-table@latest
	"dependencies": {
		"@tanstack/vue-table": "^8.20.4",

Change code and it doesn't work.(delete items from pinia store and table doesn't update).  Don't know how to fix thix
const props = defineProps<{
  columns: ColumnDef<TData, TValue>[]
  data: TData[]
}>()

const data = computed(() => props.data);

const table = useVueTable({
  data, // error here
  get columns() {
    return props.columns
  },
  getCoreRowModel: getCoreRowModel(),
  getPaginationRowModel: getPaginationRowModel(),
})

Vue: Type ComputedRef<TData[]> is missing the following properties from type TData[]: length, pop, push, concat, and 29 more
This variant  give me the same error:
const props = defineProps<{
  columns: ColumnDef<TData, TValue>[]
  data: TData[]
}>()

const {data} = toRefs(props);

const table = useVueTable({
  data,
  get columns() {
    return props.columns
  },
  getCoreRowModel: getCoreRowModel(),
  getPaginationRowModel: getPaginationRowModel(),
})

Vue: Type Ref<TData[]> is missing the following properties from type TData[]: length, pop, push, concat, and 29 more.

Same problem here, even adding a key on table with a generated hash can't force a re-render of the table :(

I have made it work with the following code:
`const props = defineProps<{
columns: ColumnDef<TData, TValue>[]
data: TData[]
}>()
const table = useVueTable({
data: toRef(props,'data'),
get columns() { return props.columns },
getCoreRowModel: getCoreRowModel(),
getFilteredRowModel: getFilteredRowModel(),
})`

To be clear, I don't think this issue is related to the UI library; all needed info is described inside the official stack/table docs, where you can find an example and how to deal with it.
Video example:
https://github.com/user-attachments/assets/02112b99-a41d-4167-954b-10caa675b989
@sadeghbarati I think we could close this issue as it is not related to shadcn-vue at all 😅

Make sense, but we need to update doc

https://tanstack.com/table/latest/docs/framework/vue/guide/table-state#using-reactive-data
https://github.com/TanStack/table/pull/5687#issuecomment-2281067245


locales config is not pulling from config file

after publishing config i noticed if you modify the locales array the values are ignored and it's still pulling from the vendor/../config

@rtorcato please check, if the issue has been resolved on v1.0.1
sorry about the delay!


Output muted

I've trained a custom voice, however, when I try to convert audio using the voice, it outputs muted audio. Is there a fix for this behavior?

What's your GPU card and the version of RVC?

This is my GPU card, the RVC I've tried again with the last one available today and still this bug

The same problem


refactor

@jonschlinkert just a quick note. to-regex — which adds non-core functionality as far as I see — adds 0.3MB of deps. That's a lot.
to-regex  │ 21          │ 0.30M

which adds non-core functionality as far as I see

Are you saying we should drop regex support from braces? How much of the 300k is safe-regex (the library that checks for catastrophic backtracking to prevent DDoS)?
If this gets too complicated I'll have to plan time in the future to work on this.

@jonschlinkert here's to-regex (it says 0.13MB but in the end it's 0.3MB)
┌─────────────────┬────────────┬───────┐
│ name            │ children   │ size  │
├─────────────────┼────────────┼───────┤
│ define-property │ 7          │ 0.11M │
├─────────────────┼────────────┼───────┤
│ extend-shallow  │ 4          │ 0.04M │
├─────────────────┼────────────┼───────┤
│ regex-not       │ 2          │ 0.02M │
├─────────────────┼────────────┼───────┤
│ safe-regex      │ 1          │ 0.02M │
├─────────────────┼────────────┼───────┤
│ 4 modules       │ 9 children │ 0.13M │
└─────────────────┴────────────┴───────┘

@jonschlinkert as far as I see from the readme there's no support for regex api in the stable version of braces. So, in this case, i'd argue for keeping the api just as simple; and adding a readme notice on how to convert to RegExps.

YAY! 🌈
Any ETA on the release?

Any ETA on the release?

it's done. I just need to wrap it up and release. probably today

Great to see one less tool (appveyor).

@paulmillr FWIW I use a tool to generate documentation, the badges are in a template, so they'll automatically be updated. The appveyor badge is excluded if there is no .appveyor.yml file.

@jonschlinkert ping!

What are you pinging about @paulmillr?

Let's release it 😃

Let's release it 😃

Are you volunteering to do the docs and changelog? :)

Working on anymatch & chokidar updates right now.

I’ve prepared new builds — Chokidar is 1/8th of previous size and feels super lean now. Can’t wait on getting these packages released!

Can’t wait on getting these packages released!

I'll be working on it this weekend.

@paulmillr how's everything working out?

@jonschlinkert it’s awesome, we’re fixing tests across platforms and waiting for node 8.16

we’re fixing tests across platforms and waiting for node 8.16

I hope I didn't break anything!


Failed to load entity kinds issue when port-forward backstage service

Hi Team,
I am trying to utilise this helm chart with only setting postgresql.enabled:true in my custom values.yaml. Both postgres and backstage pods are running fine but when I do kubectl port-forward svc/my-backstage :7007 and try to access my backstage front-end, getting below error highlighted in screenshot. Can someone please advise on the same? can't see anything suspicious in logs of backstage pod logs except below 304 status code message.
Message in backstage log:
{"level":"info","message":"::ffff:<IP_ADDRESS> - - [20/Dec/2022:20:14:05 +0000] \"GET /catalog HTTP/1.1\" 200 - \"-\" \"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.99 Safari/537.36\"","service":"backstage","type":"incomingRequest"} {"level":"info","message":"::ffff:<IP_ADDRESS> - - [20/Dec/2022:20:14:05 +0000] \"GET /favicon.ico HTTP/1.1\" 304 - \"-\" \"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.99 Safari/537.36\"","service":"backstage","type":"incomingRequest"}

Observed but apparently, there won't be any issue if you port-forward it with the command kubectl port-forward svc/my-backstage 7007:7007 where specifically we port-forward from local port 7007, weird?

Hi @NiniiGit
Without looking at this into detail, my first suspicion is that I imagine this is down to some differences between configured ports. The backstage front-end (by default) looks to port 7007 for the backend (check your application configuration to be sure). So if you let kubectl choose the local port, it will choose a port that backstage front-end isn't configured to look to. Hence why, when you set it to 7007 yourself, it works, because backstage is configured to look to that port.
I'd recommend using 7007:7007 ports as otherwise you'll run into the above.

@NiniiGit  Did you ever get to resolve the above?

@ChrisJBurns  I have faced the same issue and resolved it by adding the Envs
`- name: APP_CONFIG_backend_listen_port
value: "7007"

name: APP_CONFIG_app_baseUrl
value: "hhtps://backstage.dev.domain.io"
name: APP_CONFIG_backend_baseUrl
value: "hhtps://backstage.dev.domain.io"`

@NiniiGit did @amalcp's suggestion resolved your issue? Do you need any further assistance?

Hi @tumido  yes you can close this issue as when last time had faced this issue, I did use 7007:7007 ports as suggested by @ChrisJBurns to fix it. You can close the issue

Thank you @NiniiGit for confirming. I'm glad it's resolved.🙂 Closing now


Font size ineffective for NotoEmoji

Whatever I do and no matter the font order, NotoEmoji is always rendered in huge font (huge as in close to 10 times the bar's height), and none of size and pixelsize change the font size.
It works fine for other fonts.
The vertical offset does work.

Duplicate of #905
I wasn't able to fix it for myself, others seem to have managed though


Cannot download image

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[x] I have read the wiki page and cheat sheet, but there is no information I need.
[x] I have searched in existing issues, but did not find a same one.
[ ] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
Cannot download image. I have an image url
"https://maps.googleapis.com/maps/api/streetview?size=600x300&location=singapore 358844&pitch=15&fov=120&key=AIzaSyDFaz36_JrV22KKKTnCjEzSXsjebappKg4"
and when I pass to kingfisher in my app, it does not download the image at all.. But when I try to load the image in a browser, the image is successfully loaded, but the url is also changed to
https://maps.googleapis.com/maps/api/streetview?size=600x300&location=singapore 358844&pitch=15&fov=120&key=AIzaSyDFaz36_JrV22KKKTnCjEzSXsjebappKg4
by the browser.
Is there anything I can do to fix this?
// Edit ----------
I realise that it is the url problem, as I cannot form a proper url using the code URL(string:"urlString").. This code returns nil from the first url. Anyone knows how to fix this kind of problem?

For anyone has the same problem in future, just try to escape the string by adding
let escapeURL = urlLink.addingPercentEncoding(withAllowedCharacters: .urlQueryAllowed)!
You can try the different url character set


custom dataset : error of zerodivision

I wanted to test(no train no evaluation) my custom dataset so i made it to same format like NuScenes.
->So obviously, i made everything only except few files related with Annotation (instance.json / sample_data_annotation.json)
After that process, I success to make test.pkl and test_mono3d.json file.
And then i started to test my dataset with
torchpack dist-run -np 2 python tools/test.py configs/nuscenes/det/centerhead/lssfpn/camera/256x704/swint/default.yaml pretrained/camera-only-det.pth --format-only --eval-options 'jsonfile_prefix=./result/result.json'
and then i get
Traceback (most recent call last):
File "tools/test.py", line 232, in
main()
File "tools/test.py", line 205, in main
outputs = multi_gpu_test(model, data_loader, args.tmpdir, args.gpu_collect)
File "/home/hwi/anaconda3/lib/python3.8/site-packages/mmdet/apis/test.py", line 96, in multi_gpu_test
for i, data in enumerate(data_loader):
File "/home/hwi/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 359, in iter
return self._get_iterator()
File "/home/hwi/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 305, in _get_iterator
return _MultiProcessingDataLoaderIter(self)
File "/home/hwi/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 944, in init
self._reset(loader, first_iter=True)
File "/home/hwi/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 975, in _reset
self._try_put_index()
File "/home/hwi/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1209, in _try_put_index
index = self._next_index()
File "/home/hwi/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 512, in _next_index
return next(self._sampler_iter)  # may raise StopIteration
File "/home/hwi/anaconda3/lib/python3.8/site-packages/torch/utils/data/sampler.py", line 229, in iter
for idx in self.sampler:
File "/home/hwi/anaconda3/lib/python3.8/site-packages/mmdet/datasets/samplers/distributed_sampler.py", line 35, in iter
math.ceil(self.total_size / len(indices)))[:self.total_size]
ZeroDivisionError: division by zero
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.

mpirun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:
Process name: [[64015,1],0]
Exit code:    1
this error.
i guess 'len(indices)' is caused by data_loader
in 'test.py' but when i checked the length of dataset like 'len(cfg.data.test) it is 9.
why it is changed to 0 after processing of 'build_dataset(cfg.data.test)?
Can you give me advice to fix this error?
Thanks

Hi @SeungHwi0613,
I had a look at cfg.data.test, it seems that it is a dictionary (specified here). The reason why its length is 9 is that we have 9 keys. So it is not representing the actual size of the constructed dataset.
Regarding the division by zero error, I am not sure how you defined the dataset, but it will be helpful if you can double check whether the __len__ function is defined for your dataset. For example, if your dataset is inherited from Custom3DDataset, then the __len__ function is defined here.
Best,
Haotian

len also return 'len(self.data_infos)' this value
so
when i tried
'cfg.data.test.len()'->9 return
'dataset.len()'0 return
still same
and when i trace back to the error, mmdet/apis/test.py line70 'enumerate(data_loader)' was occuring the error i guess.
It would be so nice if you give me some advice about this error
i really appreciate about your answer.
sincerely

Hey SeungHwi0613,
I am also interested in using the code (both training and testing) on my custom dataset - could you please provide some details on the steps you made in your case?
Thank you !


bucket.strip is not a function

TypeError: bucket.strip is not a function
at Object.upload (/Users/suzhenpeng/Desktop/smemoyun/node_modules/qcloud_cos/lib/cos.js:101:19)

the same problem


Added Hub-install.py Script

Discussion Regarding the tool can be found here : https://forums.fast.ai/t/automate-hub-installation/29873/10

Awesome - thanks, @Gokkulnath!


Enable push notification service when user is blocked.

Added: https://github.com/belatrix/BackendAllStars/commit/25013288326d646ae9a546006a11a1620333f4f9


samv7: fix compile warning in PWM driver

Summary
The following warning is fixed:
chip/sam_pwm.c:961:12: warning: unused variable 'regval' [-Wunused-variable]
  961 |   uint32_t regval;

I have also added compile fixed for unused variable in serial driver.


[Feature] Add skywaliking plugin for support   Apache ShenYu (incubating) gateway

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Apache ShenYu (incubating) is a gateway,
I want to add a plugin to implement tracing for the gateway.
Use case
Achieving observability of the gateway.
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

Please assign this plugin development to me, thanks！

Assigned. Good luck.

@hutaishi I want to Shenyu community could provide a clear position about what would be the relationship between this plugin and your own agent. As I have mentioned in mail list. The shenyu's agent is very similar to (maybe from) SkyWalking's agent. I am very concerned about the conflict.

Hi，shenyu community has completely removed the agent module, so there is no conflict.

Got it.


Backend: /api/projects/update is not working

Return type of function should be a reactive Publisher in order to user @PreAuthorize annotation

There is another bug in this logic: we allow users to change project name from frontend, and before we used to save it as a new project just by passing it to repository.save. To change existing project, we should at first find it to be able to update existing entity, managed by Hibernate. And to find it, we should pass old project name along with the new one.


xfce.xfce4-timer-plugin: fix description and add longDescription

the package description seems to have been copy pasted from an other plugin
Motivation for this change
package description was wrong
Things done

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

[ ] 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 nox --run "nox-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)
[x] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@hoijui Merged in 0fbaf96c32e4abfa62f6052a768c3020a60b9dcc
Though this is without the longDescription as I feel that's more of a description of usage, and not just a longer description. Plus other plugins didn't have a longDescription.
Thanks for the fix :sparkles:


Import Northern Ireland charities

NI Charity Commission register of charities .CSV available from http://www.charitycommissionni.org.uk/charity-search/
CCNI numbers in the dataset are pure numbers (e.g. 100012), but the NI Charities can be identified with the 'NIC' prefix which I have used here (though not to the _id field)
I haven't done anything to find dual registries w.r.t. the NI charities (not quite sure what it involves or if it affects NI register). Also, the population of the NI register is still in progress so would probably put that work on hold in any case.
I've also added links to the charity pages on the respective Commission websites to the charity.html view

Hi @BobHarper1 - really sorry I've only just noticed this, not sure why I didn't get a notification.
This looks amazing. I think the last time I tried the Export CSV link from the CCNI website it only had 500 rows, but great that it's now giving all of them.
It all looks great - I'm just going to check the changes locally but they look fine to merge to me.

On the dual registration, my sense is that there's not so much overlap between the three jurastictions as there is with CCEW <> OSCR, but you'll know better than I do on that.

In terms of the ID numbers - personally I would go for "NIC101234" for the _id field, and then "101234" for ccni_number.
The justification for this would be that I'd be worried about potential collisions between the CCEW & CCNI numbers - although there's none at the moment they do both have six-digit id numbers so there's a theoretical possibility. And it makes sense if the CCNI don't use a prefix for that official number to be stored in ccni_number.
(I am slightly aware that leaving the CCEW charity numbers without a prefix seems a bit anglo-centric - I guess the justification is that it's based on the conventions generally used by charities themselves)

Hi @drkane, no problem. We're looking at making improvements to NICVA's database of vol/comm organisations through reconciling with the NI Register, as well as CCEW and OSCR, so being able to use your repo here has been a great benefit.
Some more information because I've done some work since my original message:

I also beefed up the reconcile specification so that it would work against the OpenRefine API.

I have a scraper program to get more information from the CCNI website that available from the downloadable csv, most importantly 'other names'. I'll maintain these in the Gist - fetch_data will download it from there and import_data will add it to the model.

Take your point on the _id field, yes there are some CCEW number formats that are very close to the basic CCNI format (all '10****') so wise to avoid.
I don't think there is much of an issue about dual registrations between NI > OSCR/CCEW. Any potentials I can think of are fully separate entities, for example Oxfam Ireland which is registered as an NI company. We could look and see if there are any duplicate company numbers for CCNI charities but do doubt there will be any.

@BobHarper1 great stuff - particularly doing the proper recon api which has ticked an item off my todo list! I've merged this PR and made a few more changes this afternoon.
Good to collaborate like this!


HDDS-2773. Configure Goldmark renderer

What changes were proposed in this pull request?
Enable unsafe option for the new Goldmark renderer introduced in Hugo 0.60.

unsafe
By default, Goldmark does not render raw HTMLs and potentially dangerous links. If you have lots of inline HTML and/or JavaScript, you may need to turn this on.

Also fix couple of incorrectly formatted links (no space allowed between ] and ().
https://issues.apache.org/jira/browse/HDDS-2773
How was this patch tested?
Built docs locally with Hugo 0.61.0.

Thanks @elek for reviewing and committing it.


UI Appears to be a Step Behind in Visual Updates

Godot version: 3.0.6

OS/device including version: Windows 10 (Ver 1803 Build 17134.590)
NVidia GeForce 1050 TI (Notebook) (Driver Version 419.17)

Issue description: The UI appears to be a step behind in visual updates. For instance, typing in a text field doesn't show the last character typed until another character is entered (Ex. When typing "godot", The letter 'g' will not appear until the letter 'o' is entered.)
Of course, a picture is worth a thousand words: https://streamable.com/cuxpz

Steps to reproduce:

Open Godot
Click "New Project"
Start typing in a text field, noting that it is a step behind in visual updates

Minimal reproduction project: N/A, happens on project selection

Related to #23069. But with a different graphics card/drivers?

My apologies for not finding the mentioned issue. The only other graphics card I've been able to test it on is an NVIDIA GeForce GTX 960, same Win10 and driver version, where it works fine.

Are you sure that it's running on the Nvidia GPU and not on an integrated
Intel chipset? (Godot should output which GPU is used in the terminal.)
On Sun, 24 Feb 2019, 10:26 Apprehentice<EMAIL_ADDRESS>wrote:

My apologies for not finding the mentioned issue. The only other graphics
card I've been able to test it on is an NVIDIA GeForce GTX 960, same Win10
and driver version, where it works fine.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/26222#issuecomment-466754085,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEe8mrpWnW9mF8iy4wsmyJ8_9ppWx72Eks5vQlrSgaJpZM4bOXPI
.

Forgive my ignorance, it appears that it is using the Intel(R) UHD Graphics 630 chipset. I'm in the process of downloading and installing new NVIDIA driver software to confirm that the problem is the NVIDIA chipset.

You can force using Nvidia GPU with particular software (e.g. Godot} from the NVIDIA Control Panel.

My laptop lacks the NVIDIA Control Panel for some reason, but I was able to force Godot to use the NVIDIA GPU through the Windows context menu. The problem is not present on the NVIDIA GPU and remains a problem with the Intel GPU.

Duplicate of #23069.


Multiple/duplicate Favicon requests when scrolling

Scrolling through your sections on https://projects.lukehaas.me/scrollify always triggers a request to your favicon.

On other pages with multiple favicon statements all urls are requested, when scrolling through the page...

Windows 7, Chrome stable (Version 58)
Any hints why this could be happening?

Thanks for raising this. I'm not sure why this is happening, as a guess, it could relate to the History API. Scrollify makes use of the replaceState method.

I found an open Chromium Issue https://bugs.chromium.org/p/chromium/issues/detail?id=721635 .
So this is likely a browser issue (with certain chrome versions and/or favicon notations).
Hopefully this will just go away :pray: :worried:


Configuration Checker

Automatically checks the configurations.

The allow submit / judge properties for the entities used in this contest
The availability for problem descriptions
The count of available judgehosts
The name uniqueness of team
The logo for used affiliations

Whether any team has no users
Each problem shortname should be unique within a contest
Each balloon color should be unique (?)

For problem color mapping, we can refer to
https://github.com/DOMjudge/domjudge/blob/c1e9fa849eb7b2c7df6b6e4b998ccefe74749298/webapp/src/Utils/Utils.php#L545


[BUG] Image preview not working, possibly incorrect path handling

Please confirm

[x] I am running the latest version of this plugin

Describe the bug
"File not found" error when trying to preview image under link. Also, when browsing media, the Telescope preview pane shows an error message (which I think comes from catimg): stb_image_error: No such file or directory.
To Reproduce
Steps to reproduce the behavior:

nvim first-note.md (cwd is /Users/me/zettelkasten)
Hover over the link
Call require('telekasten').preview_img()
Neovim outputs File not found: /Users/me/zettelkasten/img/pasted_img_20221014131739.png

first-note.md:
...
- ![](img/pasted_img_20221014131739.png)

relevant config bits:
local home = vim.fn.expand("~/zettelkasten")
require("telekasten").setup({
...
    home = home,
...
    img_subdir = "img",
    image_link_style = "markdown",
    media_previewer = "catimg-previewer",
...
})

Expected behavior
A preview of the image should be shown. In fact, the following works (with the exact same path listed in the "File not found" error): catimg /Users/me/zettelkasten/img/pasted_img_20221014131739.png.
Operating system (please complete the following information):

OS: macOS 11.7 (Big Sur)

@renerocksai , whenever you have time, could you look into this issue a bit? Its been 30min and I still cannot understand how/why you implemented this like that.
I solved a first issue where the img/ was duplicated in the path if the link to the file was ![](img/file.jpg).
However, telescope-media-files is still not being called properly. This is because in line 998 we expect a script of some sort for this previewer. This scrip was never part of the repo. As you are the one that made this function, maybe you have it on your machine or would be able to fix it anyway... I think it is the last stuff to do to (hopefully) close this issue.

Hi @lambtho,
The way it works is as follows: another plugin, telescope-media-files.nvim,
provides the image previewer. Hence, we need to find the path to the
previewer script. Our own telekasten.lua script is in
.../telekasten.nvim/lua/telekasten.lua. With ":h:h:h" we go up 3
directories from there, landing at ".../", one directory above the
telekasten plugin directory.  To that, we append
"telescope-media-files.nvim" and get the telescope-media-files plugin
directory. When we append "/scripts/vimg" to that, we have the path to the
previewer script of the other plugin.
Hope this helps; I am trying to recover from a cold; when I'm fit again I
shall have a look at why things might not be working. I suspect it might
have to do with the wrong cwd being passed to the previewer or the path to
the img not being correct, relative to the cwd of the called previewer.
On Sun, Feb 5, 2023 at 3:45 PM lambtho @.***> wrote:

@renerocksai https://github.com/renerocksai , whenever you have time,
could you look into this issue a bit? Its been 30min and I still cannot
understand how/why you implemented this like that.
I solved a first issue where the img/ was duplicated in the path if the
link to the file was .
However, telescope-media-files is still not being called properly. This is
because in line 998
https://github.com/renerocksai/telekasten.nvim/blob/9cbbbb697099ed1e772861b208dc1068b8b1ec07/lua/telekasten.lua#L998
we expect a script of some sort for this previewer. This scrip was never
part of the repo. As you are the one that made this function, maybe you
have it on your machine or would be able to fix it anyway... I think it is
the last stuff to do to (hopefully) close this issue.
—
Reply to this email directly, view it on GitHub
https://github.com/renerocksai/telekasten.nvim/issues/174#issuecomment-1417990469,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHLWBJ7PBZJ3USULNLE6B2LWV64JJANCNFSM6AAAAAARIKPGAQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ah, I get it now.
So I actually think I fixed the issue with my commit yesterday.  There was indeed an issue with the path. It should be all good now. Although the fix is a bit hacky and could probably be improved.

What screwed things up is that in my case is that Telekasten plugin is not installed in the same spot as other plugins. I like to have the plugins I actively develop in a local repository (~/nvim-plugins). Using lazy.nvim as my plugin manager it is then very easy to switch between the dev version and the github one. Anyway, that means that the h:h:hstuff used to go into telescope-media-files does not work and the script cannot be found.
It would probably be best to find a more robust way to call this plugin. I will open an issue for that and close this one, as commit https://github.com/renerocksai/telekasten.nvim/commit/9cbbbb697099ed1e772861b208dc1068b8b1ec07 likely fixed the problem

Actually I am reopening that. Hardcoding "ìmg/is _not ideal_ to say the least. If people were to have other images repositories such asimages/`the current "fix" would not work.
I shall revisit the patch soon to provide a proper way to figure out the actual path.


How to build a documentation badge without ReadTheDocs?

The badge in the README for documentation that was previously being generated by ReadTheDocs is no longer working because we are using our own URL. So we need to figure out how to create a badge a different way. I think.
The badge does link to the current URL however, so at least folks will be redirected to the correct place.

Go to Create status badge on the Action:

Great. Noted! Closing.


BNS Emojis not displaying

I have received a couple reports on social that a recent update has caused BNS names that contain emojis to no longer display in Leather. Would need to do more testing to confirm!
"Update to latest version it no longer shows emoji domain!"

Confirmed missing here in my wallet:

Assigning @alter-eggo, looks like this was introduced with the loading changes.


nimble: Fixed incrementing tx credits in l2cap coc layer after a packet has been sent.

In function ble_l2cap_coc_continue_tx after sending a packet tx->credits was not getting incremented. Due to this, l2cap was not able to send more packets than initial credits.
For example, after sending one packet of 512 bytes, l2cap tx credits became 0 which didn't allow sending any more packet.
Fixed it by keeping a count num_tx_credits which will keep track of credits used for a packet and after that packet has been sent tx->credit will be incremented by num_tx_credits.

Hi @sjanc, can you please take a look.

perhaps I'm missing something here, but basically your fix will return credits locally immediately after l2cap sdu was transmitted. this kind of defeats the purpose of coc where credits should be returned by peer once it can receive more data.

So ble_l2cap_chan has two separate variables for handling tx and rx credits, coc_tx and coc_rx respectively. As you said, "credits should be returned by peer once it can receive more data" is taken care by coc_rx when it's ready to receive more data. It gets assigned initial credits in ble_l2cap_coc_recv_ready once the peer is ready. In this PR, credits of coc_tx is getting incremented for sending more data once one SDU is completely sent.


api: add client bindings for the v1 API

This is the first pass for #1035. It is mostly based on https://github.com/prometheus/client_golang/pull/333 with a few changes. Notably it uses types.Silence instead of model.Silence for SilenceAPI.Get() and SilenceAPI.List() because model.Silence represents silence ID as int instead of string.
For now the client code lives in the github.com/prometheus/alertmanager/api package because it was easier this way and I didn't know where it should live otherwise.
cc @stuartnelson3

I have a vague memory of a conversation with @stuartnelson3 , concluding that the AM API client should live in github.com/prometheus/client_golang/api/alertmanager . I don't feel strongly about it. But if you put a Go client directly into the alertmanager repo, will you then also put a Java or C++ or Python client there?

I understood from this comment that the agreement was to put the client code here. But re-reading #1035, I realized that the scope was only to extract the interactions with the API from the cli package. I'll rework the PR...

Got it, so I misremembered the conclusion. All great then. Go on… :o)

@simonpasquier would you like me to take a look now, or wait until you remove [WIP]?

@stuartnelson3 wait until I remove the WIP please.

I guess leave it in cli for now, and we'll figure something out. Potentially we had lib/api or something to indicate library uses of alertmanager functionality vs. application uses.

I've added the following types to the cli package for now: Alert (used by the push alert API) and ExtendedAlert (used by the list alert API). I'm sure integrating this new code with the client code will require other changes down the road but I feel that pushing more stuff in this PR will complicate the review.


Quarm issue showing my buffs on others

This issue only seems to be on Quarm (Thanks for releasing it by the way!!)
When I cast buffs on others or my pets, regardless of the settings for the window, it doesn't show timers for those buffs. It briefly flashes the name of the person/pet I cast on, but it disappears immediately. I tried all sorts of combinations with the settings and still had the same issue, even tried redownloading it just to make sure.
The DPS Meter also doesn't appear to register up DoT Damage

ill take a look at it tomorrow (10/11) Should be ez

Can you send me some logs of DOT damage messages please. And the spell your casting on your pet

Sure thing! I'll try to get these over to you tomorrowSent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Scott @.> Date: 10/11/23  9:02 PM  (GMT-06:00) To: smasherprog/EqTool @.> Cc: sKlat @.>, Author @.> Subject: Re: [smasherprog/EqTool] Quarm issue showing my buffs on others (Issue #40)
Can you send me some logs of DOT damage messages please. And the spell your casting on your pet
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

BuffLogs.txt
Here ya go! Casted Cloud and Quickness on pet, both times the pet name flashes for a second like it registers a buff was received, but it disappears immediately. It looks very similar to what happens on P99 if I deselect other classes or tell it only count the stuff that effects me, but I've messed with those settings and it doesn't change anything.
For the DoTs, The DPS meter just registers the initial 20 damage hit, but not the DoT damage ticks.

Looks like the spells should show correctly. Please, post a screen shot of your settings.
Checking on the dps stuff now

Also in the logs you posted, are there dot damage messages? I dont play on quarm so i only log in to test things and dont have a class that has DOTs to test this out.

NM I SEE it now..
[Thu Oct 12 12:05:15 2023] a goblin warrior has taken 12 damage from your Choke.

DOT damage support added just now it should auto update soon.

can you post a pic of your settings?  I suspect you might have the checkbow for SHOW ONLY spells that effect me.
also can you confirm that dot damage now shows correctly please

Attached a screenshot of my settings, I've tried different combinations of best guess/effect me only as well as the class only stuff- still doesn't seem to work when I cast on others, it just flashes their name for a second and disappears.

DoT Damage seems to be good though!! Thank you again for taking the time to update this, especially since you're not playing on Quarm.

Very interesting. Thanks for the pic it does help.
I'll check this out.

Try checking best guess.

That checkbox is poorly named btw

For sure, I've tried it with Best guess off and on, combo'd with Effect me off and on

I AM able to reproduce the buff bugg.. trying to fix that now

FIX is live now your program should auto update and start working as expected!


Add exercise for hash

Explain what a hash it, why you need it in a holochain app.
get via entryhash
Have the exercise be a repetition of entries exercises maybe with minor extension (struct with fields?)
Let user add a test in typescript as extra learning item.

[x] write text
[x] add playground item to do a simulation
[ ] add exercise in zome
[ ] add exercise in typescript test
[ ] get feedback on text
[ ] get feedback on exercise

We can close this already right @tixel ?


newly generated node Ids don't match JSON id; problem for adding connections dynamically

Hi,
Thanks for creating and sharing this awesome library!
I tried to recreate the connections dynamically based off the JSON export object (couldn't find any code for that so figured I'd try it myself), and noticed that the ID I pass from the JSON isn't the ID for the new node.
Since I rely on the IDs from the JSON source to match the node ID when creating connections, this mismatch between the IDs makes recreating the connections unreliable.
I dug into the block.js file and found that in fact the code creates a self-incrementing numeric ID when a new Node is created.
This is brittle for several reasons:

imagine i create 10 nodes, but then delete the one with ID 7, then save the JSON, and reload. The JSON IDs will no longer match the IDs in the nodes array.

Numeric IDs get converted to string when stored and retrieved. When I tried to compare the JSON ID to the node ID, I was getting errors because I had to cast the retrieved ID to a numeric first, to get it to match the node ID.

Suggested Improvements:

When creating a new Node, the ID in the JSON (string) should be used by default, not a self-incrementing number.

block.js should use a library like uuid to create a unique ID for all new nodes (create in the UI).

Please let me know if this sounds like the right direction. Glad to do a PR.
Best Regards,
-S. Arora

Can you provide an example on jsfiddle ?

noticed that the ID I pass from the JSON isn't the ID for the new node.

During importing from JSON, node IDs are replaced with actual IDs from the data. Instances of the created nodes will have the same ID as in the data.

Numeric IDs get converted to string when stored and retrieved

Where do you store them? JSON.parse(JSON.stringify(data)) returns numberic IDs

Hi,
Appreciate the quick response!
It's not a running example, but I've copy / pasted relevant snippets here: https://jsfiddle.net/sarora/ar0kn5sh/7/

lines 88 - 100 show the main section where i'm building the connections from the JSON. Maybe I shouldn't be doing it this way??
on line 93 you can see where I have to cast the id to numeric otherwise the JSON version taken as-is is a string.

re: the fromJSON method you pointed out...is that something I'm supposed to invoke directly? In line 81 i create the push the generated node to an array of nodes, but don't do anything else fancy as you can see.
Thanks again,
-S. Arora

Starting at line 45: you shouldn't generate data based components.
Declared components are executable code that describes the behavior of your editor for a particular version.
Data only stores information about a user-created graph. Data is always dependent on components, but components shouldn't depend on data.
Can you describe your main goal?
Later I will try to describe in the visual representation the concept of this library

My overall goal is to allow users to create diagrams. Their might perhaps
10 components that can be built statically if need be..I haven’t really
started working on that part yet so was mainly using sample code for
component generation. Once a user creates a diagram I need to be able to
regenerate the diagram and allow users to modify / re-save the diagram
reliably.
On Thu, Mar 8, 2018 at 5:40 AM Vitaliy Stoliarov<EMAIL_ADDRESS>wrote:

Starting at line 45: you shouldn't generate data based components.
Declared components are executable code that describes the behavior of
your editor for a particular version.
Data only stores information about a user-created graph. Data is always
dependent on components, but components shouldn't depend on data.
Can you describe your main goal?
Later I will try to describe in the visual representation the concept of
this library
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Ni55aN/d3-node-editor/issues/57#issuecomment-371450090,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIhvdvMBJxQ6Oso4eunxvHQsDEt0uHJgks5tcQqegaJpZM4ShN9W
.

Did a little more digging and found how to invoke fromJSON method when instantiating the editor in this example: https://codepen.io/Ni55aN/pen/POWEvm?editors=1010
Will try this approach and close case if it works.
I'm still not a fan of the numeric / auto-incrementing ID due to other bug risks mentioned, but that may be a "nice to improve" item at this point. Thanks again for everything!

Thanks for pointing me in the right direction..fromJSON imported the data and setup the connections.


Update GC from dotnet/runtime

Skipping commits:
dotnet/runtime@631cb1b3dbe80c374dad691bfdd6989d8efb68d3 - I think we need to pull the Perl script to generate ETW boilerplate into the open.
dotnet/runtime@fcd862e06413a000f9cafa9d2f359226c60b9b42 - not going to mess with that right now
dotnet/runtime@6c1f8adf26cacb963e96d8f046411912aa6ebafe - I think this is for another commit that we skipped
dotnet/runtime@f99b4fe46497185db3b2049913f2af0c839fda00 - more ETW

Oh, great. Going to learn about "cgroups".

@janvorli I'm porting your change in dotnet/runtime#980 and hitting an assert:
/__w/1/s/src/Native/gc/unix/cgroup.cpp:197: static char *CGroup::FindCgroupPath(bool (*)(const char *)): Assertion `cgroup_path_relative_to_mount[common_path_prefix_len] == '/'' failed.

I added some instrumentation in 12b821d and I'm getting:
hierarchy_mount: /sys/fs/cgroup/memory
hierarchy_root: /docker/4cd7e277fcf32d39de066076dec1c716d2f1037483207344b1147130b5998e17
cgroup_path_relative_to_mount: /docker/4cd7e277fcf32d39de066076dec1c716d2f1037483207344b1147130b5998e17
common_path_prefix_len: 72

In particular the root and the path relative to mount are the same (in your examples in cgroup.cpp, there should be an extra directory in the latter).
Do you know if I'm just holding it wrong, or the code in GC doesn't handle the way Docker is configured for this particular build pool?

The assert was wrong, it didn't take into account the unnamed group case. And it was never detected as the equivalent code in the coreclr PAL's _ASSERTE was not firing due to the fact that the debugging support was not initialized at the time the cgroups were being initialized.

CI is not triggering - need to check CI status before merging.


Feature/store input data

add name attributes to input tag for autocomplete
save/restore input text to/from cookies

Thank you!
This was a place I was worrying about thinking to realize.
It is really nice to save the parameters! 😆  ❤


Is there a dev emailing list?

Hi,
I'm trying to check if airflow can be easily adapted for Hadoop ETL. Is there a developer emailing list?
More specifically, I run
export AIRFLOW_HOME=~/airflow
but I don't see ~/airflow/dags directory. Want to understand where and how to create a new workflow.
Also, is there a mechanism to set variables hierarchically so that different groups can have different
default priorities and policies.
Thanks in advance.

mkdir $AIRFLOW_HOME/dags
By variables, do you mean params or default_args. To clarify the difference, default_args are used to define default arguments for operator constructors and params are used as a set of variables that can be used in the template and the "context" which is passed around to operators execute and various callbacks.

Oh about the dev mailing list, do you mean a forum for contributors or for the community in general?
I recently created a Google group as a place holder and just now added a reference to in on the README.md, but it hasn't been used yet. I will post there when pushing new pypi release, when we have meet ups, ...
https://groups.google.com/forum/#!forum/airbnb_airflow

Oh neat - thoughts about an IRC channel too?

No IRC just yet.


menu-toogle no works

Hi, when the principal page (example: localhost:3000) is shows the menu toogle works fine and perfectly, but when i go to another route(example: localhost:3000/articles) the toogle menu no works, and the animation and effect no view in the app web.

Same issue here, looking for help

I believe it is because you are using Turbolinks


lookup istiod.istio-system.svc on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:41187-><IP_ADDRESS>:53: i/o timeout"

Bug description
the error is :
lookup istiod.istio-system.svc on <IP_ADDRESS>:53:

But my cluster IP not include IP <IP_ADDRESS>
[root@linuxtest58b5 jiaoben]# kubectl get svc -n istio-system
NAME                        TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                                                                      AGE
grafana                     ClusterIP      <IP_ADDRESS>    <none>        3000/TCP                                                                     3h41m
istio-egressgateway         ClusterIP      <IP_ADDRESS>    <none>        80/TCP,443/TCP,15443/TCP                                                     3h42m
istio-ingressgateway        LoadBalancer   <IP_ADDRESS>    <pending>     15020:25179/TCP,80:32547/TCP,443:40324/TCP,31400:52476/TCP,15443:13562/TCP   3h42m
istiod                      ClusterIP      <IP_ADDRESS>   <none>        15010/TCP,15012/TCP,443/TCP,15014/TCP,853/TCP                                3h42m
jaeger-agent                ClusterIP      None             <none>        5775/UDP,6831/UDP,6832/UDP                                                   3h41m
jaeger-collector            ClusterIP      <IP_ADDRESS>     <none>        14267/TCP,14268/TCP,14250/TCP                                                3h41m
jaeger-collector-headless   ClusterIP      None             <none>        14250/TCP                                                                    3h41m
jaeger-query                ClusterIP      <IP_ADDRESS>    <none>        16686/TCP                                                                    3h41m
kiali                       ClusterIP      <IP_ADDRESS>    <none>        20001/TCP                                                                    3h41m
kiali-operator-metrics      ClusterIP      <IP_ADDRESS>    <none>        8383/TCP,8686/TCP                                                            4d3h
prometheus                  ClusterIP      <IP_ADDRESS>    <none>        9090/TCP                                                                     3h41m
tracing                     ClusterIP      <IP_ADDRESS>    <none>        80/TCP                                                                       3h41m
zipkin                      ClusterIP      <IP_ADDRESS>   <none>        9411/TCP                                                                     3h41m

the egress pod logs:
2020-08-11T06:24:16.267602Z	error	cache	resource:default request:584bd2e3-07c2-4313-80b4-fd6fdc1fc379 CSR retrial timed out: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:41187-><IP_ADDRESS>:53: i/o timeout"
2020-08-11T06:24:16.267613Z	error	cache	resource:default failed to generate secret for proxy: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:41187-><IP_ADDRESS>:53: i/o timeout"
2020-08-11T06:24:16.267622Z	error	sds	resource:default Close connection. Failed to get secret for proxy "router~<IP_ADDRESS>~istio-egressgateway-7486cf8c97-ckklb.istio-system~istio-system.svc.cluster.local" from secret cache: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:41187-><IP_ADDRESS>:53: i/o timeout"
2020-08-11T06:24:16.267663Z	info	sds	resource:default connection is terminated: rpc error: code = Canceled desc = context canceled
2020-08-11T06:24:16.267809Z	warning	envoy config	[bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:92] StreamSecrets gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:41187-><IP_ADDRESS>:53: i/o timeout"
2020-08-11T06:24:18.035623Z	warn	Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2020-08-11T06:24:18.900319Z	info	Subchannel Connectivity change to CONNECTING
2020-08-11T06:24:18.900366Z	info	Subchannel picks a new address "istiod.istio-system.svc:15012" to connect
2020-08-11T06:24:18.900426Z	info	pickfirstBalancer: HandleSubConnStateChange: 0xc0007954b0, {CONNECTING <nil>}
2020-08-11T06:24:18.900465Z	info	Channel Connectivity change to CONNECTING
2020-08-11T06:24:19.210191Z	warning	envoy config	[bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:92] StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-08-11T06:24:19.210233Z	warning	envoy config	[bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:54] Unable to establish new stream
2020-08-11T06:24:20.035659Z	warn	Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2020-08-11T06:24:22.035476Z	warn	Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2020-08-11T06:24:22.657992Z	info	sds	resource:default new connection
2020-08-11T06:24:22.658105Z	info	sds	Skipping waiting for ingress gateway secret
2020-08-11T06:24:24.035528Z	warn	Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2020-08-11T06:24:26.035696Z	warn	Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2020-08-11T06:24:28.035739Z	warn	Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected

[root@linuxtest58b5 jiaoben]# kubectl exec istiod-788f76c8fc-qlnp4 -n istio-system --
nameserver <IP_ADDRESS>
search istio-system.svc.cluster.local svc.cluster.local cluster.local
options ndots:5

[ ] Docs
[x ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
run well
Steps to reproduce the bug
the install command :
istioctl install --set profile=demo

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
client version: 1.6.5
control plane version: 1.6.5
data plane version: 1.6.5 (8 proxies)

[root@linuxtest58b5 jiaoben]# kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:56:40Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:48:36Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

**How was Istio installed?
istioctl install --set profile=demo

Environment where bug was observed (cloud vendor, OS, etc)
one master node + three slave node, all machine is virtual machine, and in same network
centos7

<IP_ADDRESS>:53:

is your dns server
This means your DNS server is no configured properly. Did you follow the DNS steps here? https://istio.io/latest/docs/setup/install/virtual-machine/#create-files-to-transfer-to-the-virtual-machine

I solve this problem，reinstall k8s. And thanks for @howardjohn .

In my situation, the version of istio:
$ istioctl version
client version: 1.9.0
control plane version: 1.9.0
data plane version: 1.9.0 (1 proxies)

If use profile=demo to deploy istio, got the above error message:
istioctl install --set profile=demo -y

If use default profile to deploy, would not meet the above error:
istioctl install -y


feature(seo): specialized card

PR type

[x] Feature

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted screenshot of demonstrated change in this PR

Optional

[ ] I've tested PR on mobile and everything works
[ ] I found edge cases

What's new?

[x] PR closes #1136

Screenshot
Will add soon

Let's wait for xylodrone to update new cards, these seems distorted/blurred 😳
https://github.com/kodadot/nft-gallery/issues/1136#issuecomment-968760785

There is an update @roiLeo  https://github.com/kodadot/nft-gallery/issues/1136#issuecomment-968934921
Let's shoot it!

LFG, let it fly!


Typescript "as const" may break tree parsing

I encountered a weird bug:
import assert from "node:assert/strict";
import { describe, it } from "node:test";

describe("A", () => {
  describe("A.1", () => {
    it("works", async () => {
      assert.equal(1, 1);
    });

    it("breaks the tree", async () => {
      const plop = `Hello ${{ type: "extra" } as const} World`;
      assert.equal(1, 1);
    });
  });

  describe("A.2", () => {
    it("doesn't show", async () => {
      assert.equal(1, 1);
    });
  });
});

Produces the following tree:

The issue comes from ${{ type: "extra" } as const} and the following rewrites work:

Using${{ type: "extra" as const }}
Declaring const inlineObj = { type: "extra" } as const and ${inlineObj}

Just got a minimal sample repo set up here: https://github.com/yleflour/nodejs-testing-demo
I'll check out the built JS. if I have time

FYI Adding an "outDir": "./dist" and setting "emitDeclarationOnly": false in "tsconfig.json" fixes the issue as the test runner uses the .js files from the "./dist" folder
Only seem to break with on the fly transpilation

This is because we try to still parse the source naively with acorn. With acorn-loose it's often good enough but it seems like we get tripped up by this case.
While TS is technically not the only language that could transpile and get turned into JS, it's by far the most common one, so let's just ship a transpiler to deal with it properly.

I played with writing a TypeScript server plugin on https://github.com/connor4312/nodejs-testing/tree/connor4312/ts-server-plugin. The advantage is this avoids bundling anything and uses the same AST's that the server will use for general editing and might already have in memory.
Unfortunately TS parses files lazily, and the actual parsing in the TS server is a lot slower (I think just because there's more going on), resulting in a few hundred ms delay when you open a file, whereas the current implementation is fairly instant, so I don't want to ship this as-is. I think the next version of TS might bring some performance improvements in that area, so I'll let that branch hang around for a little bit and see where things go. In the meantime I'll continue looking at a simpler swap from Acorn to tree-sitter's TS grammar.

Fixed in https://github.com/connor4312/nodejs-testing/commit/08b5a2f4b6e64b9c1fe3dbd60628774cdde57e40, we will now use VS Code's TS language features to do the parsing


Performance for 10M messages via FCM?

Hi, I'm needing to send 10M desktop web pushes in < 1 hour.
So far I see a few articles about how to do this with Elixir, here's the best article I think:
https://blog.discordapp.com/how-discord-handles-push-request-bursts-of-over-a-million-per-minute-with-elixirs-genstage-8f899f0221b4
Takeaways from article:

They use Elixir (I'd rather use ruby if possible, even if it's a bit slower)
They use Google XMPP API for FCM which they say is faster
There is a limit of 100 requests in flight at a time
There is connection draining (talked about here if you search DRAINING)

Unfortunately, I can't use broadcast messages because each message is personalized.
Do you have any idea what performance would be like while using Andpush and HTTP/2 or whatever goods you got?
Cheers!

If you use HTTP/2 then your client is as optimized as it should be. Based on my research, the curb gem is the only gem that can reliably make HTTP/2 requests. Andpush has experimental support for HTTP/2, so definitely worth giving it a try if you are planning to send 10M push messages. Andpush can send about 28 messages/second, which most of the time is spent on network I/O.
Aside from HTTP/2, there are a few more optimizations you could consider evaluating:

Based on my research FCM takes about 30ms to process each request including network latency from New York, NY. If the server is physically closer to FCM's endpoint, you may be able to cut ~10ms:

((10 * 10,000,000) / (3600 * 1000) = 27.77 (hours)
where: (time saved in ms * number of messages) / convert ms to hour

Use thread-based workers like SIdekiq. If you use 99 standard dynos with 25 workers on Heroku, you may be able to send 10M messages in about 2min (excluding the time spent on generating personalized data). Even if you are not on Heroku, being able to scale workers horizontally until you hit the database limitations is very important.

(10,000,000 / (99 * 25)) * 0.03 = 121.21 (seconds)
where: (number of messages / (number of dynos * number of threads)) * time spent on each request in seconds

Finally, you may use the curb gem directly and generate JSON using only string interpolation without the JSON gem. This may sound stupid, but wrappers are performance killer, and in an extreme condition, this is a big performance boost.

Let me know if this is helpful.


Only validate OpenAPI doc files that have the versioned pattern in its name

Only validate OpenAPI doc files that have the versioned pattern in its name

@rmpalomino @nalundgaard

@anton-b can you review and merge this?


Please add TOTP (google authenticator/authy) 2 Factor Athentication

please add totp 2fa. i want my odysee account to be more secure. its pretty easy to implement so just do it.
thanks.

This is coming in a few months, being worked in an internal repo

This is coming in a few months, being worked in an internal repo

@tzarebczan, any updates regarding this?


Blog missing code

One of the last instructions on https://www.robinwieruch.de/graphql-apollo-server-tutorial/#graphql-server-data-loader-caching-batching
says:
Remember to add the loader to your subscriptions, in case you use them there:
but it just repeats the previous code. How should we add the data loader to subscriptions?

never mind didn't read the code carefully.


Change data classnames in iris.script to workaround a bug in csvgen. …

…Adapt tablenames in Jupyter notebooks. Delete unnecessary classes (created automatically by csvgen).
Also changed port mapping in docker-compose as the new superserver port by default is 1972 (not 51773 anymore)

@jtsalten  - what is the bug in csvgen? Could you please submit an issue?


Fix TypeError in scrubX()

This fixes a possible TypeError:
TypeError: Cannot use 'in' operator to search for 'x' in null

This happens because null is also an object.

This change is live in v0.2.0, which was just published.


Has anyone actually got this working? Cannot get past decode issue

I am constantly getting the error message in my logs that says the native library libstdc++.so.6 is missing, which is needed by libconnector.so. apparently.
Trying to install or update that with: sudo apt-get install libstdc++6
Just says that it's already installed and up to date.
I have tried to fix this on ubuntu, on windows, on my synology NAS. Nothing works and they all give the same error. Which leads me to believe that this bot is completely broken.
Is there a fork where it's actually working?

Nevermind, used the workaround posted here: https://github.com/vured/vured-bot/issues/40


custom event handlers

I am planing to implement functions to register custom events handlers, one for each type(GAP, GATTS and GATTC). Usage will be similar to register notify callback. Add/register custom handler:
BLEDevice::setCustomGapHandler(my_gap_event_handler);
and function to handle events:
static void my_gap_event_handler(esp_gap_ble_cb_event_t  event, esp_ble_gap_cb_param_t* param) {
	ESP_LOGW(LOG_TAG, "custom gap event handler, GAP event: %d", (uint8_t)event);
}

Function in action (logs):
W (608) SampleServer: custom gap event handler, GAP event: 0  // <-- ESP_GAP_BLE_ADV_DATA_SET_COMPLETE_EVT
W (608) SampleServer: custom gap event handler, GAP event: 1  // <-- ESP_GAP_BLE_SCAN_RSP_DATA_SET_COMPLETE_EVT
W (608) SampleServer: custom gap event handler, GAP event: 6  // <-- ESP_GAP_BLE_ADV_START_COMPLETE_EVT
W (9198) SampleServer: custom gap event handler, GAP event: 20  // <-- ESP_GAP_BLE_UPDATE_CONN_PARAMS_EVT
W (9318) SampleServer: custom gap event handler, GAP event: 20
W (9488) SampleServer: custom gap event handler, GAP event: 20
W (15848) SampleServer: custom gap event handler, GAP event: 10  // <-- ESP_GAP_BLE_SEC_REQ_EVT
W (16008) SampleServer: custom gap event handler, GAP event: 20
W (16038) BT_SMP: FOR LE SC LTK IS USED INSTEAD OF STK
W (16068) SampleServer: custom gap event handler, GAP event: 9  // <-- ESP_GAP_BLE_KEY_EVT
W (16068) SampleServer: custom gap event handler, GAP event: 9
W (16068) SampleServer: custom gap event handler, GAP event: 9
W (16078) SampleServer: custom gap event handler, GAP event: 9
W (16098) SampleServer: custom gap event handler, GAP event: 9
W (16248) SampleServer: custom gap event handler, GAP event: 9
W (16258) SampleServer: custom gap event handler, GAP event: 8  // <-- ESP_GAP_BLE_AUTH_CMPL_EVT
W (16928) SampleServer: custom gap event handler, GAP event: 20

This will allow to make library more flexible without increasing complexity and size. We can for example catch congestion events and take proper actions when we know that notify/indication cant be send.

Few more logs. Maybe its not much, but we would be allowed to override build in mechanism to achieve better performance or add something that is missing in this library. I will for sure use it to debug code.
Just a few lines of code:
....
static void my_gap_event_handler(esp_gap_ble_cb_event_t  event, esp_ble_gap_cb_param_t* param) {
	ESP_LOGW(LOG_TAG, "custom gap event handler, GAP event: %d", (uint8_t)event);
}

static void my_gattc_event_handler(esp_gattc_cb_event_t event, esp_gatt_if_t gattc_if, esp_ble_gattc_cb_param_t* param) {
	ESP_LOGW(LOG_TAG, "custom gattc event handler, GAP event: %d", (uint8_t)event);
}

static void my_gatts_event_handler(esp_gatts_cb_event_t event, esp_gatt_if_t gattc_if, esp_ble_gatts_cb_param_t* param) {
	ESP_LOGW(LOG_TAG, "custom gatts event handler, GAP event: %d", (uint8_t)event);
}
....
BLEDevice::setCustomGapHandler(my_gap_event_handler);
BLEDevice::setCustomGattsHandler(my_gatts_event_handler);
BLEDevice::setCustomGattcHandler(my_gattc_event_handler);
BLEDevice::init("My32");

Logs:
W (573) SampleServer: custom gatts event handler, GAP event: 0
W (583) SampleServer: custom gatts event handler, GAP event: 7
W (603) SampleServer: custom gatts event handler, GAP event: 9
W (603) SampleServer: custom gatts event handler, GAP event: 10
W (613) SampleServer: custom gatts event handler, GAP event: 12
W (623) SampleServer: custom gap event handler, GAP event: 0
W (623) SampleServer: custom gap event handler, GAP event: 1
W (633) SampleServer: custom gap event handler, GAP event: 6
W (111763) SampleServer: custom gatts event handler, GAP event: 14
W (112403) SampleServer: custom gap event handler, GAP event: 20
W (112513) SampleServer: custom gap event handler, GAP event: 20
W (112713) SampleServer: custom gap event handler, GAP event: 20
W (119553) SampleServer: custom gatts event handler, GAP event: 1
W (119553) SampleServer: custom gatts event handler, GAP event: 21
W (145813) SampleServer: custom gatts event handler, GAP event: 2
W (145813) SampleServer: custom gatts event handler, GAP event: 21
W (145813) SampleServer: custom gatts event handler, GAP event: 5


[SPARK-29041][PYTHON] Allows createDataFrame to accept bytes as binary type

What changes were proposed in this pull request?
This PR proposes to allow bytes as an acceptable type for binary type for createDataFrame.
Why are the changes needed?
bytes is a standard type for binary in Python. This should be respected in PySpark side.
Does this PR introduce any user-facing change?
Yes, when specified type is binary, we will allow bytes as a binary type. Previously this was not allowed in both Python 2 and Python 3 as below:
spark.createDataFrame([[b"abcd"]], "col binary")

in Python 3
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/.../spark/python/pyspark/sql/session.py", line 787, in createDataFrame
    rdd, schema = self._createFromLocal(map(prepare, data), schema)
  File "/.../spark/python/pyspark/sql/session.py", line 442, in _createFromLocal
    data = list(data)
  File "/.../spark/python/pyspark/sql/session.py", line 769, in prepare
    verify_func(obj)
  File "/.../forked/spark/python/pyspark/sql/types.py", line 1403, in verify
    verify_value(obj)
  File "/.../spark/python/pyspark/sql/types.py", line 1384, in verify_struct
    verifier(v)
  File "/.../spark/python/pyspark/sql/types.py", line 1403, in verify
    verify_value(obj)
  File "/.../spark/python/pyspark/sql/types.py", line 1397, in verify_default
    verify_acceptable_types(obj)
  File "/.../spark/python/pyspark/sql/types.py", line 1282, in verify_acceptable_types
    % (dataType, obj, type(obj))))
TypeError: field col: BinaryType can not accept object b'abcd' in type <class 'bytes'>

in Python 2:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/.../spark/python/pyspark/sql/session.py", line 787, in createDataFrame
    rdd, schema = self._createFromLocal(map(prepare, data), schema)
  File "/.../spark/python/pyspark/sql/session.py", line 442, in _createFromLocal
    data = list(data)
  File "/.../spark/python/pyspark/sql/session.py", line 769, in prepare
    verify_func(obj)
  File "/.../spark/python/pyspark/sql/types.py", line 1403, in verify
    verify_value(obj)
  File "/.../spark/python/pyspark/sql/types.py", line 1384, in verify_struct
    verifier(v)
  File "/.../spark/python/pyspark/sql/types.py", line 1403, in verify
    verify_value(obj)
  File "/.../spark/python/pyspark/sql/types.py", line 1397, in verify_default
    verify_acceptable_types(obj)
  File "/.../spark/python/pyspark/sql/types.py", line 1282, in verify_acceptable_types
    % (dataType, obj, type(obj))))
TypeError: field col: BinaryType can not accept object 'abcd' in type <type 'str'>

So, it won't break anything.
How was this patch tested?
Unittests were added and also manually tested as below.
./run-tests --python-executables=python2,python3 --testnames "pyspark.sql.tests.test_serde"

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/15430/
Test PASSed.

Merged build finished. Test PASSed.

Test build #110443 has started for PR 25749 at commit 038c7f3.

cc @ueshin @BryanCutler
BTW, I would like to backport this into branch-2.4 if you guys won't mind. The risk is super low if I am not mistaken.

Test build #110443 has finished for PR 25749 at commit 038c7f3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/110443/
Test PASSed.

@HyukjinKwon I think it was by design to only accept bytearray and not bytes in pyspark - possibly to avoid str mixup with Python 2. So I'm not sure if it is should be backported...
Otherwise, I think this is fine to allow bytes if the user specifies a binary column. And once support for Python2 is dropped, it could be inferred also.

Yea. I agree with that bytes <> str was by design so I targeted only when explicitly the type is specified. Sure, let's don't jackpot then.

Let me get this in. We should allow bytes anyway - looks Arrow converts into bytes too :D. Let me support type inference once we drop Python 2, which I will do right after Spark 3 release.

Merged to master.

Do we have a user-facing documentation about type mapping?

I don't think so. Yes so It might be better do document that. We can start to work on that after officially dropping Python 2 to reduce overhead. Python 2 and python 3 support different types and semantics (e.g., long, str <> bytes)
I don't think we have a doc for scala or java side as well actually. We should also have it, for instance, for type coercion or implicit cast rules in fact.

any chance to apply this to Spark 2.3 branch as well?
thank you.

Given the discussion above, seems we're not going to back port.

I have tested this fix with Python 2.7 and Python 3.6 with Spark 2.3.
With this run-time "patch" applied it works in both Python 2 and Python 3:
>>> import pyspark.sql.types
>>> pyspark.sql.types._acceptable_types[pyspark.sql.types.BinaryType] = (bytearray, bytes)
>>>

Output for Python 3
Using Python version 3.6.6 (default, Jun 28 2018 17:14:51)
SparkSession available as 'spark'.
>>> spark.createDataFrame([[b"abcd"]], "col binary")
Traceback (most recent call last):
. . .
TypeError: field col: BinaryType can not accept object b'abcd' in type <class 'bytes'>
>>> import pyspark.sql.types
>>> pyspark.sql.types._acceptable_types[pyspark.sql.types.BinaryType] = (bytearray, bytes)
>>>
>>> spark.createDataFrame([[b"abcd"]], "col binary")
DataFrame[col: binary]
>>>

Output for Python 2
Using Python version 2.7.15 (default, May  1 2018 23:32:55)
SparkSession available as 'spark'.
>>>
>>> spark.createDataFrame([[b"abcd"]], "col binary")
Traceback (most recent call last):
 . . .
TypeError: field col: BinaryType can not accept object 'abcd' in type <type 'str'>
>>>
>>> import pyspark.sql.types
>>> pyspark.sql.types._acceptable_types[pyspark.sql.types.BinaryType] = (bytearray, bytes)
>>>
>>> spark.createDataFrame([[b"abcd"]], "col binary")
DataFrame[col: binary]
>>>

cc @BryanCutler and @HyukjinKwon please re-evaluate backportability to Spark 2.x
thanks!!

This patch is a bit hard to say a bug fix (as pointed out at https://github.com/apache/spark/pull/25749#issuecomment-530565191) and I think that's why it was not backported ..

@HyukjinKwon @BryanCutler what do you think of adding auto inferring BinaryType for bytes, but only in python3. Given that python2 is very close to end of life and that 3.0 is a major version it seems a shame to wait to add this feature.

Hm, actually if such changes happen, 3.0 might be right place to happen. WDYT @BryanCutler? It actually will be quite breaking change.

what do you think of adding auto inferring BinaryType for bytes, but only in python3

I think this is the correct thing to do. What type is inferred now for python3 with bytes? @HyukjinKwon is this a breaking change only for Python2?

Oh, I was confused:
TypeError: not supported type: <class 'bytes'>

It's not supported yet in Python 3. Yeah, then I think it's good to do it for Python 3 only as well.

Let me create a PR.

See https://github.com/apache/spark/pull/26432


Add fallback to support coffeescript 1.x

As mentioned in https://github.com/za-creature/coffeescope/issues/31#issuecomment-335635323, it seems there's only one small fallback needed to support coffee 1.0 codebases.
(coffeescope's been a really useful part of @lever's coffeescript development...and we still have a lot of coffeescript 1.0 code 😓)

It took a bit longer to release because while testing your other PR on 1.0, I did a hackier fix (.properties?.length) and had to rebase
0.5.1 should be out containing both PRs
Thank you ⛵


Update README.md

Cleaned up the text a bit.

toru-takahashi and  ksukenoda,
Is it OK that I updated this document? Can it be pushed into production?

Yes, feel free to merge it to "master".
It's a production.


[Wait 4 #669] Fix adam iteration start to 1 at model_test

~From the paper, adam's time t start from 1. So other framework do like
iteration + 1 because they start iteration from 0. However, nntrainer
start iteration from 1 so, iteration + 1 is not correct.~
~Also, there was a bug that iteration is not counted correctly for the
train data, this patch fixes the issue~

Fix bug that epoch_idx is not saved for continue_train
Fix iteration to start from 0 in model test

Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #675. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/675-202010281432380.5793719291687-d5cf23a4ecd60afeb77cfa6053aebe82c2317439/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/675-202010281440270.48788905143738-5930d264f0a19f8ada6dec6a7736e7cce8d7311e/.

I think you are mixing epochs and iterations which are very different.

v2.

Fix bug that epoch_idx is not saved for continue_train
Fix iteration to start from 0 in model test

Fixed. Thanks :)


Russian [ru]

Me and my friend BrotiwkaS are workin on that. I translated almost 60% already.

100% translated. Im now verifying translations with my friend and Russian community.

I tested it. Its Working. Now we just need to correct some translations. And its done.
PS After that i think we need to somehow make keyboard layouts for it.

Done. We both satisfied with translation for now.
I need instructions how to make it out with Git and send a file

So it looks like i commited and pushed the file to my fork. Well. I hope my work here for now is done)

Hello! Thank you very much for making the Russian translation! You can submit it by creating a Pull request.

First Fork the repository using "Fork" in the upper right corner.
Then add the ru.json file to your fork.
Then go to "Pull Requests" on your fork and click "New Pull Request"
It should automatically setup the request to be merged into the main repository, just submit it and I'll handle the rest!

Done. Its now in the Pull Requests.

Oh and @Frooxius ... I made a accidently made a little mistake about nickname of my friend. He deleted last char of the nickname. So now he has a nickname "BrotiwkA". Not the "BrotiwkaS".
I'll fix it in translation in another update of it.

Thank you! If you want, you can still make the change to it before I merge it, so it goes right away.

@Frooxius alright. Looks like it fixed. And i even dont need to make a new Pull Request. Its was automatically pulled a new Edited file.

Added a new pull request #103 with new strings related to new Audio tools and tutorials, fixed some strings.


Fix: Update pom.xml to fix Cx3718d76a-e8e1

Jetty-xml version 11.0.12 has a vulnerability: Cx3718d76a-e8e1 3.9 Improper Restriction of XML External Entity Reference vulnerability with low severity found
I therefore think it should be

We've already looked into it and we're not affected by that vulnerability. Also, updating to Jetty 12 is both a major and breaking change that won't make it into Javalin 5, but it's being considered for Javalin 6.


The inputs to shadowed resets are identical to the corresponding non-shadowed resets. They are different wires, and sent to the blocks that have shadow logic. See for example https://cs.opensource.google/opentitan/opentitan/+/master:hw/ip/prim/rtl/prim_subreg_shadow.sv, instantiated in https://cs.opensource.google/opentitan/opentitan/+/master:hw/top_earlgrey/ip_autogen/alert_handler/rtl/alert_handler_reg_top.sv.

For this PR, all that matters is that each corresponding reset and reset_en are checked to track with at most one extra cycle delay.


Add note about limitations of the content API

This lived in the Developer Docs until this PR:
https://github.com/alphagov/govuk-developer-docs/pull/2519
It will still display in the dev docs, but will be pulled
in from here, where it is closer to the code and can be
kept up to date more consistently.

I'm not sure this makes sense in the README for the application, because from a perspective of the application it doesn't care what is in its database or not. I'm also not sure we even need this documentation anywhere as it's written in our docs for the Content API - perhaps we need to make those docs more visible?

I'd forgotten those docs exist! Fair enough - will close this PR and look at ingesting those docs into the dev docs (or at least signposting them more clearly).


[Storage] Support walk_blobs with prefix, delimiter, and versions specified

An STG85/86 feature is to support specifying prefix, delimiter, and include=versions with list_blobs (walk_blobs in this case since delimiter is used) at the same time.
This was already supported, just needed to add a test for it. Additionally, fixing up the documentation for the include keyword on walk_blobs.

API change check
API changes are not detected in this pull request.


Define namespace chip inside asn1/ASN1OID.h

Problem
asn1/ASN1OID.h is included in a namespace context.
Change overview
Move the namespace define into asn1/ASN1OID.h
Testing
Verified using unit tests.

This is a painfull review with so many files changed.
I didn't look at everything, that seems straightforward otherwise

Sorry, forget to mention. There are several patches first 3 patches are PR #9387, only last patch is the target of this PR. Please only review last patch.

This is a painfull review with so many files changed.
I didn't look at everything, that seems straightforward otherwise

Sorry, forget to mention. There are several patches first 3 patches are PR #9387, only last patch is the target of this PR. Please only review last patch.

Please write this in the summary for now. I will defer reviewing this until the other large rename is done, otherwise I also got lost in the sheer amount of deltas.


build: version 1.9.0

Custom Bush compatibility: #60 #61 #62 #63 #64 #65
new trees support for various mods: #57 #58 #59
update french i18n: #55
regular bugfixes: #51 #53

closes #11

closes #31