Unknown string ошибка - Не ошибается лишь тот, кто ничего не делает!

I wrote a function that scrapes data from a website for multiple zip codes. The code works for most zip codes, but there are some where I’m getting an Unknown String Error.

Here is the code I’m using

import time
from datetime import date, timedelta
from bs4 import BeautifulSoup
import urllib2
from dateutil.parser import parse
import pandas as pd
import random
import os
url = 'https://www.sittercity.com/jobs/search?distance=50&&page=1&per_page=100000&search_strategy=babbysitting_job&&selected_facets%5Bnew_jobs%5D=true&sort=relevance&zipcode=94513'
soup = BeautifulSoup(urllib2.urlopen(url))
posts = [t.text for t in soup.find_all(class_ = "item posted-by")]
dates = [parse(item, fuzzy = True) for item in posts]

The error is coming from the 34th item in the posts list. However the datatype of each element in the list is the same, so I’m confused. Also the 33rd item in the list seems to work. For example:

This works:

dates_single = parse(posts[32], fuzzy = True)

But this doesn’t (?)

dates_single = parse(posts[33], fuzzy = True)

Here are the values of posts[32] and posts[33]

>>> posts[33]
u'Posted by April A. on 3/28/2016'
>>> posts[32]
u'Posted by Chandrika M. on 3/30/2016'

I read through the datetil.parser documentation and none of the «Unknown String Error» use cases seem to fit.

Источник

import React from 'react';

/**
 * Translate static strings coming from the backend
 *
 * @param str: string with placeholders in the format "value is {{val: 5}}"
 * @param t: react-i18next t instance
 * @returns: translated string
 */
export default function staticTranslate(str, t) {
  if (str === undefined) {
      return str;
  }
  let substitutions = {};

  function replacer(match, p1, p2, offset, string) {
    substitutions[p1] = p2;
    return '{{' + p1 + '}}';
  }

  str = str.replace(/{{s?(w+):s?([^}]+)}}/g, replacer);
  return t(str, substitutions);
}

Источник

Your error occurs due to conflict between April (detected as month name) and 3 detected as month number.

Minimal example:

from dateutil.parser import parse
parse(u'Posted by Chandrika M. on 3/30/2016', fuzzy=True)  # datetime.datetime(2016, 3, 30, 0, 0)
parse(u'Posted by April A. on 3/28/2016', fuzzy=True)  # ValueError: Unknown string format
parse(u'Posted by XYZ A. on 3/28/2016')  #  datetime.datetime(2016, 3, 28, 0, 0)

Since your format is well-defined you may simply perform straightforward conversion, without any heuristics.

s = u'Posted by April A. on 3/28/2016'
datetime.datetime.strptime(s.split()[-1], "%m/%d/%Y")  # datetime.datetime(2016, 3, 28, 0, 0)

Источник

0

0

Моя любимая игрушка, а в Wine не запускается (
Я установил Wine последний, скопировал папку с виндой в папку ~/.wine/dosdevices/c:/Program Files , при запуске из консоли выдает такие ошибки:

[root@localhost Cossacks — Back To War]# wine dmcr
__driCreateNewScreen_20050727 — succeeded
__driCreateNewScreen_20050727 — succeeded
err:wgl:X11DRV_wglGetProcAddress (wglMakeContextCurrentARB) — not found
err:wgl:X11DRV_wglGetProcAddress (wglGetCurrentReadDCARB) — not found
err:wgl:X11DRV_wglGetProcAddress (wglCreatePbufferARB) — not found
err:wgl:X11DRV_wglGetProcAddress (wglGetPbufferDCARB) — not found
err:wgl:X11DRV_wglGetProcAddress (wglReleasePbufferDCARB) — not found
err:wgl:X11DRV_wglGetProcAddress (wglDestroyPbufferARB) — not found
err:wgl:X11DRV_wglGetProcAddress (wglQueryPbufferARB) — not found
fixme:win:EnumDisplayDevicesW ((null),0,0x34f9b8,0x00000000), stub!
fixme:d3d:IWineD3DDeviceImpl_GetAvailableTextureMem (0x11f6e0) : stub, simulating 64MB for now, returning 64MB left
fixme:ddraw:IDirectDrawImpl_SetCooperativeLevel (0x11ec50)->((nil),00000008)
, появляется черное окно, слышен фоновый звук при загрузке меню игры, но графики нету((

При запуске щелчком мыши, выдает кучу ошибок типа «Unknown string: DELSYNC (see COMMENT.TXT)»

Что делать?

Источник

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Unknown string property: ” + fieldName + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: rest and plugin.

Overview

A plugin is used to enhance the core functionalities of Elasticsearch. Elasticsearch provides some core plugins as a part of their release installation. In addition to those core plugins, it is possible to write your own custom plugins as well. There are several community plugins available on GitHub for various use cases.

Examples

Get all of the instructions for the plugin:

sudo bin/elasticsearch-plugin -h

Installing the S3 plugin for storing Elasticsearch snapshots on S3:

sudo bin/elasticsearch-plugin install repository-s3

Removing a plugin:

sudo bin/elasticsearch-plugin remove repository-s3

Installing a plugin using the file’s path:

sudo bin/elasticsearch-plugin install file:///path/to/plugin.zip

Notes and good things to know

Plugins are installed and removed using the elasticsearch-plugin script, which ships as a part of the Elasticsearch installation and can be found inside the bin/ directory of the Elasticsearch installation path.
A plugin has to be installed on every node of the cluster and each of the nodes has to be restarted to make the plugin visible.
You can also download the plugin manually and then install it using the elasticsearch-plugin install command, providing the file name/path of the plugin’s source file.
When a plugin is removed, you will need to restart every Elasticsearch node in order to complete the removal process.

Common issues

Managing permission issues during and after plugin installation is the most common problem. If Elasticsearch was installed using the DEB or RPM packages then the plugin has to be installed using the root user. Otherwise you can install the plugin as the user that owns all of the Elasticsearch files.
In the case of DEB or RPM package installation, it is important to check the permissions of the plugins directory after you install it. You can update the permission if it has been modified using the following command:

chown -R elasticsearch:elasticsearch path_to_plugin_directory

If your Elasticsearch nodes are running in a private subnet without internet access, you cannot install a plugin directly. In this case, you can simply download the plugins and copy the files inside the plugins directory of the Elasticsearch installation path on every node. The node has to be restarted in this case as well.

Log Context

Log “Unknown string property: [” + fieldName + “]”classname is RestGraphAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 if (token == XContentParser.Token.VALUE_STRING) {
 if (FIELD_NAME_FIELD.match(fieldName; parser.getDeprecationHandler())) {
 field = parser.text();
 } else {
 throw new ElasticsearchParseException("Unknown string property: [" + fieldName + "]");
 }
 }
 if (token == XContentParser.Token.VALUE_NUMBER) {
 if (SIZE_FIELD.match(fieldName; parser.getDeprecationHandler())) {
 size = parser.intValue();

See how you can use AutoOps to resolve issues

Источник