security test public no file - authorized pentest

woody-pentest-test 11 days ago

💡

Upstage Studio

아래와 같이 차단된거로 메시지가 돌아옵니다. 차단 해제 및 사유 확인 부탁드립니다. 만약 홏루 빈도가 너무 빨라서 차단이라면 호출 주기 공유 부탁드려요 ! HTTP 401: {"error":{"message":"Your API key has been blocked due to payment failure or other issues. Please check your email or contact us through Support: https://console.upstage.ai/support","type":"invalid_request_error","param":"","code":"api_key_is_blocked"}}

황상현 14 days ago

1

💡

Upstage Studio

위 오류를 내면서 401에러가 반복됩니다 너무 빠르게 호출해서 차단당한건가요? 그렇다면 어느정도의 빈도로 호출해야하는지 확인 부탁드리며 차단 해제 부탁드립니다

An Anonymous User 14 days ago

1

💡

Upstage Studio

자동 충전해도 한도가 올라가지 않습니다. - 계정: nahzkhui@gmail.com (Default Organization) - 결제 상태: Explore 커밋먼트, 월 $100 자동충전 (2026-08-23 시작, 매월 갱신 설정) - 현재 한도: Rate limit Tier 1 (Legacy) — 실측 solar-pro4 기준 100 RPM / 50,000 TPM - 사용 사례: 사내 문서·회의록 기반 AI 챗봇. RAG 특성상 호출당 입력 약 35,000~43,000 토큰이며, 본 응답 후 보조 호출(제목 생성 등)이 이어지는 구조. TPM 50,000에서는 호출 1회로 분당 예산이 소진되어 정상 사용 중에도 429가 반복 발생 (재현 예: 2026-08-23 03:06 UTC, 10:15 UTC — 첫 호출 200 성공 직후 후속 호출 3연속 429) - 요청: solar-pro4 TPM을 200,000 이상으로 상향 (최소 150,000). 개별 상향이 어렵다면 상위 커밋 티어 신청 방법 안내 - 부가 문의: 콘솔의 한도 상향 요청 폼(get.support.upstage.ai/servicedesk/customer/portal/22/create/10367)이 Not Found로 접수 불가한 상태이니 확인 부탁드립니다

An Anonymous User 22 days ago

6

💡

Upstage Studio

I'm using the Chat Completion API to request structured output, but the response is often truncated without any warning ("finish_reason":"stop"). JSON escaping often fails. Also, whether it’s because I just created the API key or because I’ve hit the rate limit, requests that initially returned a response within 10 seconds now often take over 100 or 200 seconds under the same conditions. I’ve also registered a payment method, but it doesn’t seem to make a difference. I gave up while running benchmarks to debug the "structured output" error. The model’s performance doesn’t seem bad, but the service quality makes it difficult to put it to immediate use. For reference, all service statuses are showing green. I started with `gemini-2.5-flash` to try out a Korean model or one served domestically, but switched to `solar-pro4`—it’s been quite a struggle. The sorrow of a citizen of a developing country ㅠ

노영선 about 1 month ago

2

⚙️

Upstage Console

Hi Upstage team, I wanted to share a reasoning issue I found while benchmarking Solar Pro 4 Thinking. I think it is worth looking at because this was not simply a formatting mistake or a bad final transcription, the model made a genuine logical error in both its corrected code and its follow-up explanation. I would also like to note that Ollama small q4 models (Gemma 4 31b, Qwen 27b) are able to solve this coding problem. I also tried increasing the reasoning to MAX on Open Router and it kept making the same error. The benchmark asks the model to debug a meeting-room scheduler containing exactly seven logical bugs. One of the rules is that every meeting requires exactly 15 minutes of cleanup afterward, meaning the conflict check must work symmetrically whether the new meeting comes before or after an existing booking. The correct condition is: not ( req["end"] + 15 = booking["end"] + 15 ) Solar Pro 4 instead produced: not ( req["end"] = booking["end"] + 15 ) This is asymmetric. It gives the existing booking its required cleanup period, but does not give the new request its cleanup period when the new request occurs first. That directly caused Solar to incorrectly place request R6 into Birch: R6 runs from 585–600. Birch already contains R2 starting at 600. Solar considered this valid because 600 . But R6 requires cleanup until 615, so R2 cannot start at 600. Birch is therefore unavailable, and R6 must instead be placed in Cedar. I later asked Solar why it had put R6 in Birch. Rather than recognizing the mistake, it explicitly defended the result and said: "no conflict with R2 (R2 starts at 600, after R6 ends at 600)." That follow-up is important because it confirms that this was not an accidental output mistake. The model genuinely failed to apply the cleanup constraint symmetrically. Most of the rest of the solution was strong: Solar correctly fixed the request ordering, capacity comparison, equipment comparison, deep-copy issue, room-selection ordering, and chronological output sorting. But this particular failure is significant because the benchmark specifically tests whether the model can maintain program-state constraints and correctly repair logical code. For a new model in this size/capability class, I would consider this more serious than a minor benchmark miss. The rule itself is simple and explicitly stated in the prompt, yet the model: failed to implement it correctly, produced an incorrect downstream program state, and then confidently defended the incorrect reasoning when challenged. That combination, incorrect implementation plus confident persistence after the error is pointed out, is the part I think deserves attention. I am excited to see a new contender like Sol Pro 4 in the medium sized class and will be happy to continue to test your model. I hope this is useful for evaluation and debugging. I can also provide the full benchmark prompt if that would help reproduce the issue.

An Anonymous User about 1 month ago

1

💡

Upstage Studio

Hello I was wondering if I could use Solar to improve my Korean writing skills, I’m sharing the results of my personal experiment. I hope you find this helpful.

An Anonymous User about 1 month ago

1

⚙️

Upstage Console

I'm currently training a synthetic document using the Feedback Loop feature, but I'm leaving this feedback because I've encountered one inconvenience while using it :) Currently, it seems that a warning triangle appears next to each field with a low confidence score in the extraction results, and you have to click on each one individually to confirm it as correct before it’s added to the correct answer data. However, in practice, warning indicators often appear even on values that are already correct, so as the number of documents to train increases, manually verifying each one is becoming increasingly tedious…! I’m leaving this feedback because I think it would be great to have an option to pre-enter the correct values for each document (by uploading a CSV or JSON file) and apply them all at once when the correct values are already known! That would make the schema improvement process—from the Feedback Loop to QuickTune—much smoother :) Thank you :)

[조구만 루키] 길연진 about 1 month ago

💡

Upstage Studio

The QuickTune result notification says, “Extraction quality has improved,” but but when I click that notification to view the QuickTune results, it says, “No keys with improved accuracy were found.” Since this seems to happen frequently, it’s hard to tell whether the extraction has actually improved or not. Please look into this! Thank you :)

[조구만 루키] 길연진 about 1 month ago

2

💡

Upstage Studio

I asked Solar Pro4 to populate a CSV file based on the criteria I put into a prompt. The CSV didn't appear at all even after I tried to command the same button repetitively

Hugh about 1 month ago

💡

Upstage Studio

간략히/자세히의 차이가 뭔가요?

Lucy about 2 months ago

💡

Upstage Studio

Like everyone else, I’ve been using DS V4 for a while now, and I use a variety of models—including Kimi, MIMO, OpenCode, GLM, and more—through my annual subscription. At first, just looking at the benchmark results, I thought, “Does this even mean anything to me?” But then I ran two problems through Kimi K2.6, DS V4 Flash, Solar Open2, and GPT5.6 Sol—and Solar Open2 and GPT5.6 Sol got them exactly right. This made me wonder if their actual performance in coding might be even better than what the benchmark results suggest. I’m also active in the community of a U.S.-based startup that provides OpenWeight APIs, and while discussing this, https://open2-beta.upstage.ai/ , but while some people got a 403 error, others were able to access it. I wonder if there are countries where the page doesn’t load. While international service seems unlikely due to language support issues, I thought we might be able to try it out in Korea and English-speaking regions if the performance is decent. If anyone has a trial OpenAI-compatible SolOpen2 API and key, or knows a way to top up and use it, I’d appreciate it if you could let me know.

김용태 (_) about 2 months ago

2

⚙️

Upstage Console

모아보기 보면 column명에 upscore라고 되어 있는 것으로 확인했습니다. 근데 이게 gold 기준으로 채점할 때, 밑의 레포 로직(upscore)으로 계산하는건가요?? 아니면 cell 단위로 채점하는건가요?? https://github.com/UpstageAI/UpScore

wooseoksong about 2 months ago

1

💡

Upstage Studio

https://console.upstage.ai/ko/docs/integrations/claude-code 모델을 바꿔도 같은 에러 메시지나 나오네요 현재 지원을 안하는 걸까요??

차원준 about 2 months ago

3

⚙️

Upstage Console

안녕하세요. 혹시 solar-pro2 로 추론하면 그룹 항목에서 특정 key 기준으로 unique한 행만 남기는 그런 로직도 있나요??ㅠ

wooseoksong about 2 months ago

1

💡

Upstage Studio

스키마 수정하고 실행하려니 workflow has been deleted라고 뜨며 안됩니다.

Hugo 2 months ago

💡

Upstage Studio

현재 파이썬으로 requests 라이브러리를 사용하고 있습니다. Document Parser의 API로 호출했을 때 request_id로 KILL을 하거나 Cancel 하는 방법이 있나요? 공식 페이지를 찾아봤을 때 관련 내용이 없어서 문의드립니다. 빠른 답변 부탁드립니다.

정수민 2 months ago

5

💡

Upstage Studio

계정 간 에이전트 JSON 이동이 안되는 것 같습니다. 다른 계정에서 만든 에어전트를 내보낸 후 가져오기를 하였는데 다음과 같은 에러가 납니다!

길연진 3 months ago

2

💡

Upstage Studio

좌측 사이드바에서 업로드한 파일명을 변경할 수 있으면 좋을 것 같습니다!

[조구만 루키] 길연진 3 months ago

1

💡

Upstage Studio